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:32:53 -0400 |
| commit | 3f783c882712db5a5e0056f271ff765edeb2571a (patch) | |
| tree | e1c81292d7aa479a77723bd82589c846b4c94458 /src/backend/parser | |
| parent | 530acda4dabe26a4345eccd28a92dd23b1e7a94a (diff) | |
| download | postgresql-3f783c882712db5a5e0056f271ff765edeb2571a.tar.gz postgresql-3f783c882712db5a5e0056f271ff765edeb2571a.zip | |
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/backend/parser')
| -rw-r--r-- | src/backend/parser/gram.y | 1 |
1 files changed, 1 insertions, 0 deletions
diff --git a/src/backend/parser/gram.y b/src/backend/parser/gram.y index 7c8dc500880..50942267500 100644 --- a/src/backend/parser/gram.y +++ b/src/backend/parser/gram.y @@ -8669,6 +8669,7 @@ explain_option_elem: explain_option_name: NonReservedWord { $$ = $1; } + | analyze_keyword { $$ = "analyze"; } ; explain_option_arg: |