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

From Daniel Gustafsson
Subject Re: Using Valgrind to detect faulty buffer accesses (no pin or buffer content lock held)
Date
Msg-id DAD9210C-A229-4B17-9F10-634A45832ED5@yesql.se
Whole thread Raw
In response to Re: Using Valgrind to detect faulty buffer accesses (no pin or buffercontent lock held)  (Peter Geoghegan <pg@bowt.ie>)
Responses Re: Using Valgrind to detect faulty buffer accesses (no pin or buffer content lock held)  (Peter Geoghegan <pg@bowt.ie>)
List pgsql-hackers
> On 26 Apr 2020, at 02:17, Peter Geoghegan <pg@bowt.ie> wrote:

> Attached is v2 of the patch series.

This patch fails to apply to HEAD due to conflicts in nbtpage.c, can you please
submit a rebased version?

cheers ./daniel


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: estimation problems for DISTINCT ON with FDW
Next
From: Alvaro Herrera
Date:
Subject: Re: Auxiliary Processes and MyAuxProc