Re: plan shape work

Andy Fan <zhihuifan1213@163.com>

From: Andy Fan <zhihuifan1213@163.com>

To: Robert Haas <robertmhaas@gmail.com>

Cc: PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>

Date: 2025-05-22T08:14:23Z

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 →

Assign each subquery a unique name prior to planning it.
- 8c49a484e8eb 19 (unreleased) landed
Keep track of what RTIs a Result node is scanning.
- f2bae51dfd5b 19 (unreleased) landed

Andy Fan <zhihuifan1213@163.com> writes:

>
>> This list of elided nodes is stored in the PlannedStmt
>
> I did a quick check on the attached patches and I can see some more
> information is added into PlannedStmt. then my question are the
> PlannedStmt is not avaiable during the future planning cycle, then how
> does these information would be helpful on the feture planning? and I'm
> strange that there are little changes on the optimizer part. Does this
> patchset just a preparation work for reconstructing a same plan in
> future? 

I'm sure it is a preliminary work for reconstructing a same plan in
future, sorry for this noise. 

-- 
Best Regards
Andy Fan