From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
---|---|
To: | Andres Freund <andres(at)anarazel(dot)de> |
Cc: | Richard Guo <guofenglinux(at)gmail(dot)com>, 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-07-19 18:45:01 |
Message-ID: | CA+TgmobwVwqXZcNUYmkZG-RhvoQ+5m5pczQij7rurTcng0fD8w@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Thu, Jul 4, 2024 at 5:52 PM Andres Freund <andres(at)anarazel(dot)de> wrote:
> As-is they can't be backpatched, unless I am missing something? Afaict they
> introduce rather thorough ABI breaks? And API breaks, actually?
Aside from that, this looks quite invasive for back-patching, and the
number of bug reports so far suggest that we should be worried about
more breakage appearing later.
However, that leaves us in a situation where we have no back-patchable
fix for a bug which causes queries to return the wrong answer, which
is not a great situation.
Is there a smaller fix that we could commit to fix the bug?
--
Robert Haas
EDB: http://www.enterprisedb.com
From | Date | Subject | |
---|---|---|---|
Next Message | Nathan Bossart | 2024-07-19 18:45:49 | Re: Remove dependence on integer wrapping |
Previous Message | Laurenz Albe | 2024-07-19 18:41:50 | Re: Incremental backup from a streaming replication standby fails |