Re: GROUP BY ROLLUP queries on views trigger full table scans (index usage not optimized)

From: Richard Guo <guofenglinux(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Haowu Ge <gehaowu(at)bitmoe(dot)com>, pgsql-bugs <pgsql-bugs(at)lists(dot)postgresql(dot)org>
Subject: Re: GROUP BY ROLLUP queries on views trigger full table scans (index usage not optimized)
Date: 2025-12-30 03:47:51
Message-ID: CAMbWs49hJwP92mB5GFdj06cgH553SbbSNQZR2NnLD6VG6e00rg@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Mon, Dec 29, 2025 at 1:51 AM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> So here, I think the don't-break-things rule points towards
> back-patching.

Thanks for the confirmation. I've pushed this patchset and
back-patched it to v18.

Thanks for the report, Haowu. The fix will be in the next minor
release, scheduled for February.

- Richard

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Amit Kapila 2025-12-30 06:55:37 Re: BUG #19360: Bug Report: Logical Replication initial sync fails with "conflict=update_origin_differs" PG12 toPG18
Previous Message Japin Li 2025-12-30 02:30:24 Re: BUG #19367: typos in backend/utils/adt/timestamp.c