Re: Wrong results with grouping sets
Tom Lane <tgl@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Robert Haas <robertmhaas@gmail.com>
Cc: Andres Freund <andres@anarazel.de>, Richard Guo <guofenglinux@gmail.com>,
PostgreSQL-development <pgsql-hackers@postgresql.org>
Date: 2024-07-19T19:22:57Z
Lists: pgsql-hackers
Commits
Same data as JSON:
GET /api/v1/messages/:b64id/commits
the thread's linked commits as JSON, with link sources.
API reference →
-
Remove the RTE_GROUP RTE if we drop the groupClause
- ffe12d1d22e7 18.0 landed
-
Mark expressions nullable by grouping sets
- f5050f795aea 18.0 landed
-
Introduce an RTE for the grouping step
- 247dea89f761 18.0 landed
Robert Haas <robertmhaas@gmail.com> writes: > On Thu, Jul 4, 2024 at 5:52 PM Andres Freund <andres@anarazel.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. Yeah, 0 chance of back-patching this. If we had more confidence in it maybe we could see our way to putting it in v17, but I fear that would be tempting the software gods. It needs to get through a full beta test cycle. > 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. It's not; but this has been wrong since grouping sets were put in, yet the number of field reports so far can probably still be counted without running out of fingers. I'm content if we can fix it going forward, and would not expend a lot of effort on a probably-futile search for a fix that doesn't involve a query data structure change. (I'm aware that I ought to review this patch, and will try to make time for that before the end of the CF.) regards, tom lane