Re: plan shape work

Robert Haas <robertmhaas@gmail.com>

From: Robert Haas <robertmhaas@gmail.com>

To: Alexandra Wang <alexandra.wang.oss@gmail.com>

Cc: PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>, "bruce@momjian.us" <bruce@momjian.us>, lepihov@gmail.com

Date: 2025-09-02T20:07:17Z

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

v3-0003-Assert-that-RTIs-of-joined-rels-are-discoverable-.patch (application/octet-stream) patch v3-0003
v3-0001-Keep-track-of-what-RTIs-a-Result-node-is-scanning.patch (application/octet-stream) patch v3-0001
v3-0002-Consider-a-Result-node-s-relids-in-ExplainPreScan.patch (application/octet-stream) patch v3-0002
v3-0004-Give-subplans-names-that-are-known-while-planning.patch (application/octet-stream) patch v3-0004
v3-0005-Store-information-about-range-table-flattening-in.patch (application/octet-stream) patch v3-0005
v3-0007-Store-information-about-Append-node-consolidation.patch (application/octet-stream) patch v3-0007
v3-0006-Store-information-about-elided-nodes-in-the-final.patch (application/octet-stream) patch v3-0006

On Thu, Aug 28, 2025 at 1:22 PM Alexandra Wang
<alexandra.wang.oss@gmail.com> wrote:
> Thanks for the patches!

Thanks for the review. Responding just briefly to avoid quoting too much text:

- I'm glad to hear that you like 0002 and consider it an improvement
independent of what follows.
- I'm glad to hear that you're OK with the current split between 0001 and 0002.
- I would like opinions on those topics from more people.
- I have attempted to fix all of the other mistakes that you pointed
out in the attached v3, which is also rebased.

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