Re: Valgrind - showing memory leaks

=?utf-8?Q?=C3=81lvaro?= Herrera <alvherre@kurilemu.de> writes:
> On 2025-May-08, Tom Lane wrote:
>> So it seems like valgrind is wrong here, or else we're leaking the
>> whole rd_att structure later on somehow.

> Well, the problem is that if num_check is zero, FreeTupleDesc() doesn't
> free ->check.

Ah-hah.

> Done that way, thanks.

Thanks! I've been putting together a list of fixes to make
Valgrind less noisy, and it just got one shorter.

            regards, tom lane