Re: Using Valgrind to detect faulty buffer accesses (no pin or buffer content lock held)

Peter Geoghegan <pg@bowt.ie>

From: Peter Geoghegan <pg@bowt.ie>

To: Daniel Gustafsson <daniel@yesql.se>

Cc: Andres Freund <andres@anarazel.de>, Alvaro Herrera <alvherre@2ndquadrant.com>, Masahiko Sawada <masahiko.sawada@2ndquadrant.com>, PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>

Date: 2020-07-02T17:11:53Z

Lists: pgsql-hackers

Attachments

v3-0002-Add-nbtree-Valgrind-buffer-lock-checks.patch (application/octet-stream) patch v3-0002
v3-0001-Add-Valgrind-buffer-access-instrumentation.patch (application/octet-stream) patch v3-0001

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

Commits

Add nbtree Valgrind buffer lock checks.
- 4a70f829d86c 14.0 landed
Add Valgrind buffer access instrumentation.
- 1e0dfd166b3f 14.0 landed
Fix bug in nbtree VACUUM "skip full scan" feature.
- b0229f26da75 13.0 cited
Fix another minor page deletion buffer lock issue.
- 7154aa16a64d 13.0 landed
Fix minor nbtree page deletion buffer lock issue.
- fa7ff642c22c 13.0 landed
Skip full index scan during cleanup of B-tree indexes when possible
- 857f9c36cda5 11.0 cited