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-WzkQhGE4Z5U-W-cXpYQTsp7C7_mt8y+y1zj-n9nqyo6+rQ@mail.gmail.com
Whole thread Raw
In response to Re: Using Valgrind to detect faulty buffer accesses (no pin or buffer content lock held)  (Daniel Gustafsson <daniel@yesql.se>)
Responses Re: Using Valgrind to detect faulty buffer accesses (no pin or buffer content lock held)  (Georgios Kokolatos <gkokolatos@protonmail.com>)
Re: Using Valgrind to detect faulty buffer accesses (no pin or buffer content lock held)  (Anastasia Lubennikova <a.lubennikova@postgrespro.ru>)
List pgsql-hackers
On Thu, Jul 2, 2020 at 7:48 AM Daniel Gustafsson <daniel@yesql.se> wrote:
> This patch fails to apply to HEAD due to conflicts in nbtpage.c, can you please
> submit a rebased version?

I attach the rebased patch series.

Thanks
-- 
Peter Geoghegan

Attachment

pgsql-hackers by date:

Previous
From: Pavel Stehule
Date:
Subject: Re: proposal: unescape_text function
Next
From: Jaka Jančar
Date:
Subject: Re: Sync vs Flush