| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Lukas Fittl <lukas(at)fittl(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Jacob Champion <jacob(dot)champion(at)enterprisedb(dot)com>, Dian Fay <di(at)nmfay(dot)com>, Matheus Alcantara <matheusssilv97(at)gmail(dot)com>, Jakub Wartak <jakub(dot)wartak(at)enterprisedb(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: pg_plan_advice |
| Date: | 2026-01-29 13:35:43 |
| Message-ID: | CA+TgmoaUfjdBrWD_ZnTkBduUKMkOLdchOjr9wy4phVJB7SFi=g@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, Jan 29, 2026 at 12:45 AM Lukas Fittl <lukas(at)fittl(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Amit Kapila | 2026-01-29 13:36:33 | Re: pgsql: Prevent invalidation of newly synced replication slots. |
| Previous Message | Robert Haas | 2026-01-29 13:34:25 | Re: pg_plan_advice |