Re: GROUP BY ROLLUP queries on views trigger full table scans (index usage not optimized) - Mailing list pgsql-bugs

From Haowu Ge
Subject Re: GROUP BY ROLLUP queries on views trigger full table scans (index usage not optimized)
Date
Msg-id 0f894411-0d2c-4455-8403-f342642e49bc@bitmoe.com
Whole thread Raw
In response to Re: GROUP BY ROLLUP queries on views trigger full table scans (index usage not optimized)  (Richard Guo <guofenglinux@gmail.com>)
List pgsql-bugs
On 12/24/25 15:50, Richard Guo wrote:
> On Thu, Dec 18, 2025 at 5:56 PM Richard Guo <guofenglinux@gmail.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


Attachment

pgsql-bugs by date:

Previous
From: Amit Langote
Date:
Subject: Re: BUG #19355: Attempt to insert data unexpectedly during concurrent update
Next
From: Tender Wang
Date:
Subject: Re: BUG #19355: Attempt to insert data unexpectedly during concurrent update