Re: Query Performance Degradation Due to Partition Scan Order – PostgreSQL v17.6

From: Andrei Lepikhov <lepihov(at)gmail(dot)com>
To: Adrien Nayrat <adrien(dot)nayrat(at)anayrat(dot)info>, pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: Query Performance Degradation Due to Partition Scan Order – PostgreSQL v17.6
Date: 2025-09-09 07:02:01
Message-ID: 8556ec5a-aa4a-4e1f-82d0-ea1a6e283b12@gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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(at)gmail(dot)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

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Dilip Kumar 2025-09-09 07:12:00 Re: [PATCH] Accept connections post recovery without waiting for RemoveOldXlogFiles
Previous Message Amit Kapila 2025-09-09 06:58:25 Re: [PATCH] Accept connections post recovery without waiting for RemoveOldXlogFiles