Request a Demo
Home   >   mailing lists

Re: Query Performance Degradation Due to Partition Scan Order – PostgreSQL v17.6 - Mailing list pgsql-hackers

From Andrei Lepikhov
Subject Re: Query Performance Degradation Due to Partition Scan Order – PostgreSQL v17.6
Date
Msg-id 8556ec5a-aa4a-4e1f-82d0-ea1a6e283b12@gmail.com
Whole thread Raw
In response to Re: Query Performance Degradation Due to Partition Scan Order – PostgreSQL v17.6  (Adrien Nayrat <adrien.nayrat@anayrat.info>)
List pgsql-hackers
Tree view 
On 8/9/2025 12:32, Adrien Nayrat wrote:
> On 9/8/25 12:05 PM, Andrei Lepikhov wrote:
>> On 8/9/2025 11:47, Ashutosh Bapat wrote:
>>> On Mon, Sep 8, 2025 at 4:01 AM Vivek Gadge <vvkgadge56@gmail.com> wrote:
> It reminds me of these threads :
Yes, partially. Actively using foreign tables and touching cheaper 
partitions first is crucial in queries with limits. Also, some cases may 
provide an implicit limit, like a merge join.

-- 
regards, Andrei Lepikhov

pgsql-hackers by date:

Previous
From: Amit Kapila
Date:
Subject: Re: [PATCH] Accept connections post recovery without waiting for RemoveOldXlogFiles
Next
From: Dilip Kumar
Date:
Subject: Re: [PATCH] Accept connections post recovery without waiting for RemoveOldXlogFiles