Re: pgsql: Allow for plugin control over path generation strategies. - Mailing list pgsql-committers

From Michael Paquier
Subject Re: pgsql: Allow for plugin control over path generation strategies.
Date
Msg-id aXrnPgrq6Gggb5TG@paquier.xyz
Whole thread Raw
In response to pgsql: Allow for plugin control over path generation strategies.  (Robert Haas <rhaas@postgresql.org>)
Responses Re: pgsql: Allow for plugin control over path generation strategies.
Re: pgsql: Allow for plugin control over path generation strategies.
List pgsql-committers
Hi Robert,

On Wed, Jan 28, 2026 at 05:08:03PM +0000, Robert Haas wrote:
> Allow for plugin control over path generation strategies.

I am not sure what is going on here, but skink has gone rogue since
this has been committed.  The first failure of this animal points to
this commit:
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=skink&dt=2026-01-28%2017%3A12%3A26

Some details from postmaster.log:
==2296443== Conditional jump or move depends on uninitialised value(s)
==2296443==    at 0x434D3E6: cost_material (costsize.c:2593)
==2296443==    by 0x436E869: materialize_finished_plan (createplan.c:6531)
[...]
**2296443** Valgrind detected 1 error(s) during execution of "explain
(costs off) declare c1 scroll cursor for select (select 42) as x;"
**2296443** Valgrind detected 1 error(s) during execution of "declare
c1 scroll cursor for select (select 42) as x;"

So it looks like this is missing some initialization, causing valgrind
to complain.
--
Michael

Attachment

pgsql-committers by date:

Previous
From: Michael Paquier
Date:
Subject: pgsql: Add test doing some cloning of extended statistics data
Next
From: Michael Paquier
Date:
Subject: pgsql: Fix two error messages in extended_stats_funcs.c