Re: RFC: extensible planner state

Tom Lane <tgl@sss.pgh.pa.us>

From: Tom Lane <tgl@sss.pgh.pa.us>
To: Robert Haas <robertmhaas@gmail.com>
Cc: PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Date: 2025-09-24T16:18:22Z
Lists: pgsql-hackers
Robert Haas <robertmhaas@gmail.com> writes:
> Here's a new set of patches. I've added a new 0001 at the beginning to
> fix the bug you identified in SetExplainExtensionState; this will need
> to be back-patched to v18 once the release freeze lifts.

I'm good with 0001, and the release freeze is over, so push that
whenever you like.  I'll try to look at the rest soon.

			regards, tom lane



Commits

  1. Add extension_state member to PlannedStmt.

  2. Add planner_setup_hook and planner_shutdown_hook.

  3. Add ExplainState argument to pg_plan_query() and planner().

  4. Remove PlannerInfo's join_search_private method.

  5. Allow private state in certain planner data structures.

  6. Fix array allocation bugs in SetExplainExtensionState.

  7. Make it possible for loadable modules to add EXPLAIN options.