]> granicus.if.org Git - postgresql/commit
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:33:18 +0000 (13:33 -0400)
commit940a85e5e1c32d479d43df89c410195063e786d2
tree54838532308c6c02e5969cc808a93d384bdb560c
parentf94979f618abffb63cad2266f39db8beeeb18afc
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