Re: plan shape work

Robert Haas <robertmhaas@gmail.com>

From: Robert Haas <robertmhaas@gmail.com>

To: Tom Lane <tgl@sss.pgh.pa.us>

Cc: Richard Guo <guofenglinux@gmail.com>, Alexandra Wang <alexandra.wang.oss@gmail.com>, PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>, "bruce@momjian.us" <bruce@momjian.us>, lepihov@gmail.com

Date: 2025-09-11T20:07:03Z

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

Attachments

v5-0003-Ensure-that-all-joinrel-RTIs-are-discoverable-fro.patch (application/octet-stream) patch v5-0003
v5-0001-Keep-track-of-what-RTIs-a-Result-node-is-scanning.patch (application/octet-stream) patch v5-0001
v5-0002-Consider-a-Result-node-s-relids-in-ExplainPreScan.patch (application/octet-stream) patch v5-0002

Here's a likely-doomed new version of just the first three patches.
0002 is unchanged. 0001 has been reworked so that a Result node
contains a result_type. This is as per Tom's suggestion, but it's
unclear to me that he will like the details. 0003 has been reworked so
that when we build a Join plan, we annotate it with the ojrelids
completed at that level, which Tom said earlier that he thought was
the wrong idea (but after I'd already written the code, and I've
already replied to say I don't understand what the alternative is).

Hence, I expect this version to crash and burn, but maybe it will do
so in such a way that I have some idea what to propose instead.

--
Robert Haas
EDB: http://www.enterprisedb.com