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 11:17:18
Message-ID: 38b0e248-0ce4-4f16-9b6e-cb558b5014ee@postgrespro.ru
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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.

--
Regards,
Alena Rybakina
Postgres Professional

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Bertrand Drouvot 2025-03-03 11:54:39 Re: [BUG]: the walsender does not update its IO statistics until it exits
Previous Message Amit Kapila 2025-03-03 11:11:38 Re: Add an option to skip loading missing publication to avoid logical replication failure