Movatterモバイル変換

[0]ホーム
URL:

Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

 Sign up
Appearance settings

Commit3f783c8

Browse files
committed
Put analyze_keyword back in explain_option_name production.
In commit2c92eda, I broke "EXPLAIN(ANALYZE)" syntax, because I mistakenly thought that ANALYZE/ANALYSE wereonly partially reserved and thus would be included in NonReservedWord;but actually they're fully reserved so they still need to be called outhere.A nicer solution would be to demote these words to type_func_name_keywordstatus (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 breaksECPG'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 previouscommit.
1 parent530acda commit3f783c8

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
@@ -8669,6 +8669,7 @@ explain_option_elem:
86698669

86708670
explain_option_name:
86718671
NonReservedWord{$$ =$1; }
8672+
|analyze_keyword{$$ ="analyze"; }
86728673
;
86738674

86748675
explain_option_arg:

0 commit comments

Comments
 (0)
[8]ページ先頭
©2009-2025 Movatter.jp