Re: Why our Valgrind reports suck

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Richard Guo <guofenglinux(at)gmail(dot)com>
Cc: Andres Freund <andres(at)anarazel(dot)de>, Álvaro Herrera <alvherre(at)kurilemu(dot)de>, pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: Why our Valgrind reports suck
Date: 2025-08-03 02:03:49
Message-ID: 319763.1754186629@sss.pgh.pa.us
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

I wrote:
> Richard Guo <guofenglinux(at)gmail(dot)com> writes:
>> This is very useful work; I hope we can get it in soon.

> Thanks for looking at it!

Pushed, after squashing related commits, changing the pq_mq_handle
bit as you suggested, and fixing one more leak report that I don't
think was there in May. There's still work to be done here, but
now we have a pretty good foundation for chasing remaining leaks.

regards, tom lane

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Xuneng Zhou 2025-08-03 06:02:54 Re: Bug in pg_dump --filter? - Invalid object types can be misinterpreted as valid
Previous Message Fujii Masao 2025-08-03 01:56:05 Re: Assertion failure in pgbench