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
v5-0003-Ensure-that-all-joinrel-RTIs-are-discoverable-fro.patch
Description: Binary data
v5-0001-Keep-track-of-what-RTIs-a-Result-node-is-scanning.patch
Description: Binary data
v5-0002-Consider-a-Result-node-s-relids-in-ExplainPreScan.patch
Description: Binary data
