Re: BUG #19837: ORDER BY/DISTINCT ON use wrong column with grouping set duplicates

From: Andrey Rachitskiy <pl0h0yp1(at)gmail(dot)com>
To: 125atishprak(at)gmail(dot)com, pgsql-bugs(at)lists(dot)postgresql(dot)org
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Subject: Re: BUG #19837: ORDER BY/DISTINCT ON use wrong column with grouping set duplicates
Date: 2026-11-14 10:50:33
Message-ID: CAB8bMit-EGwQVTAnSoxaqhDSpFKFj3=7Jx11iMAjB0YMcypuKQ@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

сб, 14 нояб. 2026 г. в 02:17, Andrey Rachitskiy <pl0h0yp1(at)gmail(dot)com>:

>
> 0001 fixes the ROLLUP query. The nulling bit from f5050f795ae was
> attached to ai2, which is in every grouping set, so ai1 never got it.
>
>
Attached v2 for 0001 — code unchanged, only the test was fixed.

Attachment Content-Type Size
v2-0001-Bind-repeated-grouping-expressions-to-their-own-sort.patch text/x-patch 8.4 KB

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Zsolt Parragi 2026-11-14 14:22:44 Re: BUG #19897: Recovery fails after "LOG: consistent recovery state reached"
Previous Message Dilip Kumar 2026-11-14 10:48:29 Re: BUG #19864: pg_get_publication_tables() gets cache lookup error after concurrent DROP PUBLICATION