Re: Non-reproducible valgrind failure on HEAD

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: Non-reproducible valgrind failure on HEAD
Date: 2021-05-09 21:12:14
Message-ID: 539828.1620594734@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Andres Freund <andres(at)anarazel(dot)de> writes:
> On 2021-05-09 15:29:06 -0400, Tom Lane wrote:
>> One point worth mentioning is that I'd forgotten to build with
>> "#define USE_VALGRIND" in the first try. AFAIK that should make
>> valgrind strictly less sensitive, so I think it's not material,
>> but still.

> I think it may be material - see the comments in
> AddCatcacheInvalidationMessage().

Ah-hah. Please excuse the noise.

(I wonder if we shouldn't adjust the comments in pg_config_manual.h,
though, as they certainly leave the impression that USE_VALGRIND
isn't essential.)

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Andres Freund 2021-05-09 21:17:50 Re: Non-reproducible valgrind failure on HEAD
Previous Message Andres Freund 2021-05-09 21:02:55 Re: Non-reproducible valgrind failure on HEAD