Re: RFC: extensible planner state - Mailing list pgsql-hackers

From Robert Haas
Subject Re: RFC: extensible planner state
Date
Msg-id CA+TgmoZwqO=0HoVvYnWX6YaK5Jvov2A3YhqTjgAUVG4tCxHxHQ@mail.gmail.com
Whole thread Raw
In response to Re: RFC: extensible planner state  (Robert Haas <robertmhaas@gmail.com>)
List pgsql-hackers
On Fri, Sep 5, 2025 at 4:19 PM Robert Haas <robertmhaas@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

Attachment

pgsql-hackers by date:

Previous
From: Nathan Bossart
Date:
Subject: Re: GetNamedLWLockTranche crashes on Windows in normal backend
Next
From: Sami Imseih
Date:
Subject: Re: GetNamedLWLockTranche crashes on Windows in normal backend