diff options
| author | Tom Lane <tgl@sss.pgh.pa.us> | 2013-06-05 13:32:53 -0400 |
|---|---|---|
| committer | Tom Lane <tgl@sss.pgh.pa.us> | 2013-06-05 13:33:05 -0400 |
| commit | 48b5120977e20aef92a080002966ee95e4005d39 (patch) | |
| tree | d3407cfe0d649ebecbf3bc2e124e0dd89605b64b /src/tutorial/funcs_new.c | |
| parent | 75b161d015c49e211224cbe3c8c8a009bfea368e (diff) | |
Put analyze_keyword back in explain_option_name production.
In commit 2c92edad48796119c83d7dbe6c33425d1924626d, I broke "EXPLAIN
(ANALYZE)" syntax, because I mistakenly thought that ANALYZE/ANALYSE were
only partially reserved and thus would be included in NonReservedWord;
but actually they're fully reserved so they still need to be called out
here.
A nicer solution would be to demote these words to type_func_name_keyword
status (they can't be less than that because of "VACUUM [ANALYZE] ColId").
While that works fine so far as the core grammar is concerned, it breaks
ECPG's grammar for reasons I don't have time to isolate at the moment.
So do this for the time being.
Per report from Kevin Grittner. Back-patch to 9.0, like the previous
commit.
Diffstat (limited to 'src/tutorial/funcs_new.c')
0 files changed, 0 insertions, 0 deletions