Horton

Re: RFC: extensible planner state

Robert Haas <robertmhaas@gmail.com>

View thread View on postgr.es
From: Robert Haas <robertmhaas@gmail.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Date: 2025-09-29T13:28:55Z
Lists: pgsql-hackers 
On Sun, Sep 28, 2025 at 11:41 AM Tom Lane <tgl@sss.pgh.pa.us> wrote:
> Robert Haas <robertmhaas@gmail.com> writes:
> > Done now. Here's a rebase of the rest, plus I tweaked the GEQO patch
> > to try to avoid a compiler warning that cfbot was complaining about.
>
> I'm good with the v7 patch set, except for the complaint I raised
> previously that we really ought to have more than zero documentation
> for planner()'s parameters.  If you don't care to write such text,
> attached is a cut at it.

Oh, nice, thanks! I'm going to be on vacation the rest of this week so
I plan to deal with this next week. However, if you feel like
committing it before then, please feel free.

-- 
Robert Haas
EDB: http://www.enterprisedb.com

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.