Re: pgsql: Allow for plugin control over path generation strategies.

From: Aleksander Alekseev <aleksander(at)tigerdata(dot)com>
To: pgsql-committers(at)lists(dot)postgresql(dot)org
Cc: Michael Paquier <michael(at)paquier(dot)xyz>, Robert Haas <rhaas(at)postgresql(dot)org>
Subject: Re: pgsql: Allow for plugin control over path generation strategies.
Date: 2026-01-29 13:48:47
Message-ID: CAJ7c6TOZwau0vYMHK5Z0e4PF7MCj9QNX2n5PU5XR6eh0_w6LbQ@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-committers

Hi,

> 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.

I tested an alternative solution based on memset() and it makes
Valgrind happy (tested on Linux x64), while all the tests pass.

--
Best regards,
Aleksander Alekseev

Attachment Content-Type Size
v1-0001-Initialize-mathpath-variable-in-materialize_finis.patch application/x-patch 899 bytes

In response to

Browse pgsql-committers by date

  From Date Subject
Next Message Aleksander Alekseev 2026-01-29 13:53:29 Re: pgsql: Allow for plugin control over path generation strategies.
Previous Message Amit Kapila 2026-01-29 13:36:33 Re: pgsql: Prevent invalidation of newly synced replication slots.