database/postgres
1
0
Fork 0
mirror of https://github.com/postgres/postgres.git synced 2026-01-05 23:38:41 +03:00
Code Activity

Remove the RTE_GROUP RTE if we drop the groupClause

Browse Source 
For an EXISTS subquery, the only thing that matters is whether it
returns zero or more than zero rows.  Therefore, we remove certain SQL
features that won't affect that, among them the GROUP BY clauses.

After we drop the groupClause, we'd better remove the RTE_GROUP RTE
and clear the hasGroupRTE flag, as they depend on the groupClause.
Failing to do so could result in a bogus RTE_GROUP entry in the parent
query, leading to an assertion failure on the hasGroupRTE flag.

Reported-by: David Rowley
Author: Richard Guo
Discussion: https://postgr.es/m/CAApHDvp2_yht8uPLyWO-kVGWZhYvx5zjGfSrg4fBQ9fsC13V0g@mail.gmail.com
This commit is contained in:
Richard Guo
2024-10-25 09:52:34 +09:00
parent d32d146399
commit ffe12d1d22
3 changed files with 47 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

8
src/test/regress/sql/join.sql
View File

@@ -818,6 +818,14 @@ explain (costs off)
select a.* from tenk1 a left join tenk1 b on a.unique1 = b.unique2
where b.unique2 is null;
--
-- regression test for bogus RTE_GROUP entries
--
explain (costs off)
select a.* from tenk1 a
where exists (select 1 from tenk1 b where a.unique1 = b.unique2 group by b.unique1);
--
-- regression test for proper handling of outer joins within antijoins
--