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

From Robert Haas
Subject Re: RFC: extensible planner state
Date
Msg-id CA+TgmoZ3mOt=op-wONtUULthM_ViJ5nrswuDh_01_oB2yxVSGA@mail.gmail.com
Whole thread Raw
In response to Re: RFC: extensible planner state  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On Tue, Aug 19, 2025 at 2:28 PM Tom Lane <tgl@sss.pgh.pa.us> wrote:
> You'll presumably have to use GetMemoryChunkContext() for RelOptInfo,
> so I don't see much downside from using it in one or even both of the
> other cases too.

Pointer dereference must be faster than a function call.

> Hm.  We don't have read support for these structs, so maybe it's fine.
> It looks weird though.

Left this one as-is for now.

Here's v2. 0001 is what you saw before with an attempt to fix the
memory context handling. 0002 removes join_search_private. All I've
tested is that the tests pass.

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

Attachment

pgsql-hackers by date:

Previous
From: Kirk Wolak
Date:
Subject: Re: Retail DDL
Next
From: Nathan Bossart
Date:
Subject: Re: Don't treat virtual generated columns as missing statistics in vacuumdb --missing-stats-only