Re: pgsql: Introduce CompactAttribute array in TupleDesc

From: David Rowley <dgrowleyml(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-committers(at)lists(dot)postgresql(dot)org
Subject: Re: pgsql: Introduce CompactAttribute array in TupleDesc
Date: 2024-12-04 12:45:50
Message-ID: CAApHDvqEPBMb-1dum-_JePUhnrzcuSWBp9TJSbv7XBQ8J1oi-w@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

On Tue, 3 Dec 2024 at 17:55, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Just a gut-level guess, but I'm wondering about something like
> uninitialized fields that happen to work as long as the memory
> was zero to start with. A run under valgrind might offer insight.

Thanks. I've written about the cause of this in [1].

David

[1] https://postgr.es/m/CAApHDvq%3DGXX%2Bf75AqSGX4JGvtCAXydsOWzNdOSnQNjxwtnG-Aw%40mail.gmail.com

In response to

Browse pgsql-committers by date

  From Date Subject
Next Message Peter Eisentraut 2024-12-04 15:44:59 pgsql: Fix dead code
Previous Message John Naylor 2024-12-04 10:12:45 pgsql: Fix use-after-free in parallel_vacuum_reset_dead_items