Horton

Re: Considering fractional paths in Append node

Alena Rybakina <a.rybakina@postgrespro.ru>

View thread
From: Alena Rybakina <a.rybakina@postgrespro.ru>
To: Andrei Lepikhov <lepihov@gmail.com>
Cc: Alexander Korotkov <aekorotkov@gmail.com>, Nikita Malakhov <hukutoc@gmail.com>, Andy Fan <zhihuifan1213@163.com>, pgsql-hackers <pgsql-hackers@postgresql.org>, Tom Lane <tgl@sss.pgh.pa.us>, David Rowley <dgrowleyml@gmail.com>
Date: 2025-03-03T11:17:18Z
Lists: pgsql-hackers

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

  1. Teach Append to consider tuple_fraction when accumulating subpaths.

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