Re: Why our Valgrind reports suck

From: "David E(dot) Wheeler" <david(at)justatheory(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Alexander Lakhin <exclusion(at)gmail(dot)com>, Richard Guo <guofenglinux(at)gmail(dot)com>, 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: 2026-06-12 07:19:51
Message-ID: F0F46216-C2B3-4548-9B73-B0B4863D8548@justatheory.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Jun 10, 2026, at 22:53, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:

> or, actually, the bug's not so old: apparently I broke it in
> e78d1d6d4. Where's my brown paper bag?

Oh man, now I want to know what this references!

D

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Fujii Masao 2026-06-12 07:27:56 Re: Add “FOR UPDATE NOWAIT” lock details to the log.
Previous Message Roman Khapov 2026-06-12 07:08:29 LDAP timeout options