Re: Considering fractional paths in Append node

From: Alena Rybakina <a(dot)rybakina(at)postgrespro(dot)ru>
To: Andrei Lepikhov <lepihov(at)gmail(dot)com>
Cc: Alexander Korotkov <aekorotkov(at)gmail(dot)com>, Nikita Malakhov <hukutoc(at)gmail(dot)com>, Andy Fan <zhihuifan1213(at)163(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, David Rowley <dgrowleyml(at)gmail(dot)com>
Subject: Re: Considering fractional paths in Append node
Date: 2025-03-03 16:34:04
Message-ID: ecb40fa3-e590-42f4-a675-8756af6fdb94@postgrespro.ru
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 03.03.2025 14:17, Alena Rybakina wrote:
> Hi! Thank you for your work on this subject.
>
> I agree with your code but one phrase in commit message was confusing
> for me:
>
> "This change is dedicated to more active usage of IndexScan and
> parameterised
> NestLoop paths in partitioned cases under an Append node, as it
> already works
> with plain tables."
>
> As I understood this thread is about the optimization that allows
> considering Index Scan if we need the limited number of rows and
> later the commit message contains it. I didn't understand completely
> the sentence above to be honest.
>
>
Sorry for noise, I understood it and I think everything is fine there.

--
Regards,
Alena Rybakina
Postgres Professional

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Ashutosh Bapat 2025-03-03 16:34:16 Re: Statistics Import and Export: difference in statistics dumped
Previous Message Nathan Bossart 2025-03-03 16:33:37 Re: PATCH: warn about, and deprecate, clear text passwords