On Thu, Nov 5, 2026 at 5:29 PM Richard Guo <[email protected]> wrote: > Given the wrong results, I think we need to reconsider back-patching > to v16. Is fixing this in the back branches worth the risk of an ABI > break?
I searched some open-source extensions and found several that allocate their own PlannerInfo, such as TimescaleDB, HypoPG and pg_ivm, and Apache AGE even passes one to flatten_join_alias_vars. This close to the minor releases, I didn't want to risk an ABI break, so I've pushed it to master and v19 only. (v16-v18 still give these wrong results silently, but I don't know what to do about them for now.) - Richard
