aboutsummaryrefslogtreecommitdiff
path: root/contrib/jsonb_plpython/sql/jsonb_plpython.sql
diff options
context:
space:
mode:
authorTom Lane <tgl@sss.pgh.pa.us>2024-10-14 15:41:42 -0400
committerTom Lane <tgl@sss.pgh.pa.us>2024-10-14 15:42:02 -0400
commit9812138593f3e56735d93715a6dc2ed2d392611e (patch)
treee515db3455b43ac2303e140211e7e2380b81f092 /contrib/jsonb_plpython/sql/jsonb_plpython.sql
parentf244a2bb4c5520fc0271e638598abcbe7c9bc8cf (diff)
downloadpostgresql-9812138593f3e56735d93715a6dc2ed2d392611e.tar.gz
postgresql-9812138593f3e56735d93715a6dc2ed2d392611e.zip
ecpg: avoid breaking the IDENT precedence level in two.
Careless string hacking caused parse.pl to transform gram.y's declaration %nonassoc IDENT PARTITION RANGE ROWS ... into %nonassoc IDENT %nonassoc CSTRING PARTITION RANGE ROWS ... It turns out that this has no semantic impact, because the generated preproc.c is exactly the same either way (if you inject a blank line to keep line numbers the same). Nonetheless, given the great emphasis that the commentary in gram.y places on keeping those other keywords at the same precedence level as IDENT, this seems like foolishly risking ecpg behaving differently from the core parser. Adjust the code so that CSTRING is added to the precedence line without breaking it into two lines. Discussion: https://postgr.es/m/2157151.1713540065@sss.pgh.pa.us
Diffstat (limited to 'contrib/jsonb_plpython/sql/jsonb_plpython.sql')
0 files changed, 0 insertions, 0 deletions