Horton

Re: RFC: extensible planner state

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

View thread View on postgr.es
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:49:14Z
Lists: pgsql-hackers 
Robert Haas <robertmhaas@gmail.com> writes:
> Cool... except I thought that the release freeze wouldn't lift until
> we release, which I thought was tomorrow?

Nope, the freeze is over as soon as the git tag for the release is
pushed, cf

https://wiki.postgresql.org/wiki/Committing_checklist#Release_freezes

We'd unfreeze when the stamping commit is made, except that we want
some breathing room for a re-wrap if a packager discovers a critical
problem.  We give them 24 hours to report that.

(What happens if a critical problem is discovered shortly later?
We'd probably use a new minor release number in that case.)

			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.