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-05T17:38:43Z

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

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

On Fri, Sep 5, 2025 at 12:40 PM Robert Haas <robertmhaas@gmail.com> wrote:
> Ah, well then Richard's idea might work! Let me try it and see what happens...

Here's the result. Seem to work OK.

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