8000 Put analyze_keyword back in explain_option_name production. · sqlparser/postgres@53eb835 · GitHub
[go: up one dir, main page]

Skip to content

Commit 53eb835

Browse files
committed
Put analyze_keyword back in explain_option_name production.
In commit 2c92eda, 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.
1 parent c28bfb3 commit 53eb835

File tree

1 file changed

+1
-0
lines changed

1 file changed

+1
-0
lines changed

src/backend/parser/gram.y

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -6980,6 +6980,7 @@ explain_option_elem:
69806980

69816981
explain_option_name:
69826982
NonReservedWord { $$ = $1; }
6983+
| analyze_keyword { $$ = "analyze"; }
69836984
;
69846985

69856986
explain_option_arg:

0 commit comments

Comments
 (0)
0