On Fri, Sep 5, 2025 at 4:19 PM Robert Haas <robertmh...@gmail.com> wrote: > While mulling this over, I realized that this only works if you don't > mind propagating information into the final plan regardless without > knowing whether or not EXPLAIN was actually used. That's pretty sad, [...] > The simplest idea that comes to mind for me is to make pg_plan_query() > take an ExplainState * argument and pass it through to planner().
Here's a new version that implements this idea and also cleans up a few points that Melanie noted. -- Robert Haas EDB: http://www.enterprisedb.com
v4-0003-Add-ExplainState-argument-to-pg_plan_query-and-pl.patch
Description: Binary data
v4-0002-Remove-PlannerInfo-s-join_search_private-method.patch
Description: Binary data
v4-0004-Add-planner_setup_hook-and-planner_shutdown_hook.patch
Description: Binary data
v4-0001-Allow-private-state-in-certain-planner-data-struc.patch
Description: Binary data
v4-0005-Add-extension_state-member-to-PlannedStmt.patch
Description: Binary data
v4-0006-not-for-commit-count-distinct-joinrels-and-joinre.patch
Description: Binary data
