diff options
author | Tom Lane <tgl@sss.pgh.pa.us> | 2021-06-01 11:12:56 -0400 |
---|---|---|
committer | Tom Lane <tgl@sss.pgh.pa.us> | 2021-06-01 11:12:56 -0400 |
commit | dc272157a8aa1764aa92c013a2813d300f6ca32a (patch) | |
tree | a259fe7965c162b39a9a81c4d9c7412ceb8b345c /src/bin/scripts/common.c | |
parent | fe194f731fbf6ea0d8c08bdd41edd0a2db52a643 (diff) | |
download | postgresql-dc272157a8aa1764aa92c013a2813d300f6ca32a.tar.gz postgresql-dc272157a8aa1764aa92c013a2813d300f6ca32a.zip |
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/bin/scripts/common.c')
0 files changed, 0 insertions, 0 deletions