Re: pg_plan_advice - Mailing list pgsql-hackers

From Robert Haas
Subject Re: pg_plan_advice
Date
Msg-id CA+TgmoaUfjdBrWD_ZnTkBduUKMkOLdchOjr9wy4phVJB7SFi=g@mail.gmail.com
Whole thread Raw
In response to Re: pg_plan_advice  (Lukas Fittl <lukas@fittl.com>)
List pgsql-hackers
On Thu, Jan 29, 2026 at 12:45 AM Lukas Fittl <lukas@fittl.com> wrote:
> The indirect relationship between those functions doesn't seem great
> (i.e. anything that gets read in cost_material has to be initialized
> in materialize_finished_plan). What if we just zero initialize the
> dummy Path structure instead, like in the attached?

This might be the right answer, but I didn't want to add more memory
zeroing than needed without discussion, so I have just pushed a
minimal fix for now. Thanks for the analysis.

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



pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: pg_plan_advice
Next
From: Amit Kapila
Date:
Subject: Re: pgsql: Prevent invalidation of newly synced replication slots.