Re: Why our Valgrind reports suck

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Andres Freund <andres(at)anarazel(dot)de>
Cc: pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: Why our Valgrind reports suck
Date: 2025-05-10 02:58:36
Message-ID: 589429.1746845916@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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

In response to

Browse pgsql-hackers by date

  From Date Subject
Previous Message Masahiko Sawada 2025-05-10 00:57:35 Re: Make COPY format extendable: Extract COPY TO format implementations