Re: Why our Valgrind reports suck

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Peter Geoghegan <pg(at)bowt(dot)ie>
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-05-23 17:39:15
Message-ID: 2566869.1748021955@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Peter Geoghegan <pg(at)bowt(dot)ie> writes:
> On Fri, May 23, 2025 at 11:42 AM Andres Freund <andres(at)anarazel(dot)de> wrote:
>>> I'm envisioning this patch series as v19 work, were you
>>> thinking we should be more aggressive?

>> Mostly agreed - but I am wondering if the AV fix should be backpatched?

> I think that it probably should be.

Yeah, I agree, but didn't get to that yet. I've also gone ahead with
committing a couple of clear bugs that I located while doing this.

regards, tom lane

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2025-05-23 17:52:01 Re: PATCH: jsonpath string methods: lower, upper, initcap, l/r/btrim, replace, split_part
Previous Message Florents Tselai 2025-05-23 17:06:25 Re: PATCH: jsonpath string methods: lower, upper, initcap, l/r/btrim, replace, split_part