summaryrefslogtreecommitdiff
path: root/src/backend/commands/constraint.c
diff options
context:
space:
mode:
authorTom Lane <tgl@sss.pgh.pa.us>2021-06-01 11:12:56 -0400
committerTom Lane <tgl@sss.pgh.pa.us>2021-06-01 11:12:56 -0400
commit39862dde4beecdf1c5f84a20fe3bb6f4ba928edb (patch)
tree1e69ee82c86ad1d7ad79c2e49dbfc1d310670a70 /src/backend/commands/constraint.c
parentf9e35ff236c9d12c4c30a17f2c09cad56dbf65bb (diff)
Reject SELECT ... GROUP BY GROUPING SETS (()) FOR UPDATE.
This case should be disallowed, just as FOR UPDATE with a plain GROUP BY is disallowed; FOR UPDATE only makes sense when each row of the query result can be identified with a single table row. However, we missed teaching CheckSelectLocking() to check groupingSets as well as groupClause, so that it would allow degenerate grouping sets. That resulted in a bad plan and a null-pointer dereference in the executor. Looking around for other instances of the same bug, the only one I found was in examine_simple_variable(). That'd just lead to silly estimates, but it should be fixed too. Per private report from Yaoguang Chen. Back-patch to all supported branches.
Diffstat (limited to 'src/backend/commands/constraint.c')
0 files changed, 0 insertions, 0 deletions