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-WznX4dpvdhuqwGjCZwVzt1oBSaF0-tt6vsfS1jQLcbJ8iw@mail.gmail.com
Whole thread Raw
In response to Re: Using Valgrind to detect faulty buffer accesses (no pin or buffer content lock held)  (Peter Geoghegan <pg@bowt.ie>)
List pgsql-hackers
On Fri, Jul 17, 2020 at 5:53 PM Peter Geoghegan <pg@bowt.ie> wrote:
> Pushed the first patch just now, and intend to push the other one soon. Thanks!

Pushed the second piece of this (the nbtree patch) just now.

Thanks for the review!
-- 
Peter Geoghegan



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: v13 planner ERROR: could not determine which collation to use for string comparison
Next
From: Peter Geoghegan
Date:
Subject: Re: Index Skip Scan (new UniqueKeys)