Re: Why our Valgrind reports suck - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Why our Valgrind reports suck
Date
Msg-id 589429.1746845916@sss.pgh.pa.us
Whole thread Raw
In response to Re: Why our Valgrind reports suck  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Why our Valgrind reports suck
List pgsql-hackers
I wrote:
> One thing I noticed while reading the Valgrind manual is that
> they describe a facility for "two level" tracking of custom
> allocators such as ours.

And, since there's nothing new under the sun around here,
we already had a discussion about that back in 2021:

https://www.postgresql.org/message-id/flat/3471359.1615937770%40sss.pgh.pa.us

That thread seems to have led to fixing some specific bugs,
but we never committed any of the discussed valgrind infrastructure
improvements.  I'll have a go at resurrecting that...

            regards, tom lane



pgsql-hackers by date:

Previous
From: Masahiko Sawada
Date:
Subject: Re: Make COPY format extendable: Extract COPY TO format implementations
Next
From: Bruce Momjian
Date:
Subject: Re: PG 18 release notes draft committed