Postgres Pro
Downloads
Home   >   mailing lists

Re: Using Valgrind to detect faulty buffer accesses (no pin or buffer content lock held) - Mailing list pgsql-hackers

From Peter Geoghegan
Subject Re: Using Valgrind to detect faulty buffer accesses (no pin or buffer content lock held)
Date
Msg-id CAH2-WzmF0ECfd04uy6ONBBE6RYfTXB3=wxzO36C4rKrWygvKsQ@mail.gmail.com
Whole thread Raw
In response to Re: Using Valgrind to detect faulty buffer accesses (no pin or buffer content lock held)  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
Tree view 
On Sat, Jul 18, 2020 at 7:36 PM Tom Lane <tgl@sss.pgh.pa.us> wrote:
> I wonder whether skink's failure today is due to this change:
>
> https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=skink&dt=2020-07-18%2018%3A01%3A10

That seems extremely likely. I think that I need to do something like
what you see in the attached.

Anyway, I'll take care of it tomorrow. Sorry for missing it before my commit.

-- 
Peter Geoghegan
Attachment

pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Using Valgrind to detect faulty buffer accesses (no pin or buffer content lock held)
Next
From: Andy Fan
Date:
Subject: Re: [PATCH] Keeps tracking the uniqueness with UniqueKey