Put analyze_keyword back in explain_option_name production.
authorTom Lane <tgl@sss.pgh.pa.us>
Wed, 5 Jun 2013 17:32:53 +0000 (13:32 -0400)
committerTom Lane <tgl@sss.pgh.pa.us>
Wed, 5 Jun 2013 17:32:53 +0000 (13:32 -0400)
commit3f783c882712db5a5e0056f271ff765edeb2571a
treee1c81292d7aa479a77723bd82589c846b4c94458
parent530acda4dabe26a4345eccd28a92dd23b1e7a94a
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.
src/backend/parser/gram.y