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

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

On 12/24/25 15:50, Richard Guo wrote:
> On Thu, Dec 18, 2025 at 5:56 PM Richard Guo <guofenglinux(at)gmail(dot)com> wrote:
>> Upon closer look, it seems that we do not need the syntactic scope
>> check at all, as long as we ensure that phnullingrels is empty. In
>> this case, the PHV is either a no-op (from a reduced outer join) or
>> used for identity separation (grouping sets). In either case, the PHV
>> is transparent regarding the value, so it should not prevent the
>> underlying expression from matching the index.
>
> Here is the updated version along the lines of this idea.
>
> - Richard

Tested and passed in both example and production environments. Thank you
for your work.

--
Thanks & Best Regards
👨‍💻 Haowu Ge (葛豪武) | 🌐 www.gehaowu.com | 📡 BG5FRG | 🔐 0xDF09D8A8

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Tender Wang 2025-12-24 12:07:00 Re: BUG #19355: Attempt to insert data unexpectedly during concurrent update
Previous Message Amit Langote 2025-12-24 08:08:33 Re: BUG #19355: Attempt to insert data unexpectedly during concurrent update