From: | Richard Guo <guofenglinux(at)gmail(dot)com> |
---|---|
To: | David Rowley <dgrowleyml(at)gmail(dot)com> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Wrong results with grouping sets |
Date: | 2024-10-10 09:51:12 |
Message-ID: | CAMbWs4-+bgaaGPCKr14q5L4v3neqx2te31_O8QJN61XY7i7x-A@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Thu, Oct 10, 2024 at 4:06 PM Richard Guo <guofenglinux(at)gmail(dot)com> wrote:
> While we can fix this issue by propagating the hasGroupRTE mark from
> the EXISTS subquery to the parent, a better fix might be to remove the
> subquery's RTE_GROUP entry, since we have dropped the subquery's
> groupClause before the pull-up (see simplify_EXISTS_query).
Here is the patch.
Thanks
Richard
Attachment | Content-Type | Size |
---|---|---|
v1-0001-Remove-the-RTE_GROUP-RTE-if-we-drop-the-groupClause.patch | application/octet-stream | 3.7 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Aleksander Alekseev | 2024-10-10 10:16:14 | Re: Build issue with postgresql 17 undefined reference to `pg_encoding_to_char' and `pg_char_to_encoding' |
Previous Message | Aleksander Alekseev | 2024-10-10 09:49:38 | Re: Build issue with postgresql 17 undefined reference to `pg_encoding_to_char' and `pg_char_to_encoding' |