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
-
Add extension_state member to PlannedStmt.
- 4685977cc51c 19 (unreleased) landed
-
Add planner_setup_hook and planner_shutdown_hook.
- 94f3ad3961a2 19 (unreleased) landed
-
Add ExplainState argument to pg_plan_query() and planner().
- c83ac02ec730 19 (unreleased) landed
-
Remove PlannerInfo's join_search_private method.
- 64095d157482 19 (unreleased) landed
-
Allow private state in certain planner data structures.
- 0132dddab33a 19 (unreleased) landed
-
Fix array allocation bugs in SetExplainExtensionState.
- 694057d236b1 18.1 landed
- 803ef0ed49ee 19 (unreleased) landed
-
Make it possible for loadable modules to add EXPLAIN options.
- c65bc2e1d14a 18.0 cited