aboutsummaryrefslogtreecommitdiff
path: root/src/backend/access/gist/gistproc.c
diff options
context:
space:
mode:
authorTom Lane <tgl@sss.pgh.pa.us>2011-05-05 20:38:52 -0400
committerTom Lane <tgl@sss.pgh.pa.us>2011-05-05 20:38:52 -0400
commit12b7164578e73abb065a835c588c1e0c44670ed3 (patch)
tree8eac7a2764042dfc7c79494af9f8531676871268 /src/backend/access/gist/gistproc.c
parent27525b183189487c674f24620e608298ac0c8e29 (diff)
downloadpostgresql-12b7164578e73abb065a835c588c1e0c44670ed3.tar.gz
postgresql-12b7164578e73abb065a835c588c1e0c44670ed3.zip
Remove precedence labeling of keywords TRUE, FALSE, UNKNOWN, and ZONE.
These were labeled with precedences just to avoid attaching explicit precedences to the productions in which they were the last terminal symbol. Since a terminal symbol precedence marking can affect many other things too, it seems like better practice to attach precedence labels to the productions, and not mark the terminal symbols. Ideally we'd also remove the precedence attached to NULL_P, but it turns out that we are actually depending on that having a precedence higher than POSTFIXOP, else we get a shift/reduce conflict for postfix operators in b_expr. (Which more or less proves my point about these markings having a high risk of unexpected consequences.) For the moment, move NULL_P into the set of keywords grouped with IDENT, so that at least it will act similarly to non-keywords; and document the interaction.
Diffstat (limited to 'src/backend/access/gist/gistproc.c')
0 files changed, 0 insertions, 0 deletions