Horton

Re: Considering fractional paths in Append node

Andy Fan <zhihuifan1213@163.com>

View thread
From: Andy Fan <zhihuifan1213@163.com>
To: Nikita Malakhov <hukutoc@gmail.com>
Cc: Andrei Lepikhov <lepihov@gmail.com>, pgsql-hackers <pgsql-hackers@postgresql.org>, Tom Lane <tgl@sss.pgh.pa.us>, David Rowley <dgrowleyml@gmail.com>
Date: 2024-10-19T00:03:57Z
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.

Nikita Malakhov <hukutoc@gmail.com> writes:

Hi Nikita,

> Hi!
>
> Andy, one quick question - what do you think on using
> root->limit_tuples as a guidance on how many 
> rows we have to consider in plans cost?

Within my exprerience, the committer probabaly dislikes the idea of
"ignoring  the difference of tuple_fraction between subquery level and
RelOptInfo level" and the committers dislikes a complex soluation like
what I did in [1]. Maybe you can try to figure out completed and simple
soluation to make everyone happy, but I have no idea about on this right
now. 

[1]
https://www.postgresql.org/message-id/CAApHDvry0nSV62kAOH3iccvfPhGPLN0Q97%2B%3Db1RsDPXDz3%3DCiQ%40mail.gmail.com

-- 
Best Regards
Andy Fan