| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Richard Guo <guofenglinux(at)gmail(dot)com>, Alexandra Wang <alexandra(dot)wang(dot)oss(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, "bruce(at)momjian(dot)us" <bruce(at)momjian(dot)us>, lepihov(at)gmail(dot)com |
| Subject: | Re: plan shape work |
| Date: | 2025-09-11 20:07:03 |
| Message-ID: | CA+TgmoapsySgZ2xtfiG4Kvb8pw7xC7P_uwq0ZOBvvYmgw8q64w@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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
| Attachment | Content-Type | Size |
|---|---|---|
| v5-0003-Ensure-that-all-joinrel-RTIs-are-discoverable-fro.patch | application/octet-stream | 17.1 KB |
| v5-0001-Keep-track-of-what-RTIs-a-Result-node-is-scanning.patch | application/octet-stream | 66.6 KB |
| v5-0002-Consider-a-Result-node-s-relids-in-ExplainPreScan.patch | application/octet-stream | 8.7 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Euler Taveira | 2025-09-11 20:38:23 | Re: Unexpected changes of CurrentResourceOwner and CurrentMemoryContext |
| Previous Message | Tom Lane | 2025-09-11 19:34:47 | Re: race condition in pg_class |