Re: Shared buffer access rule violations? - Mailing list pgsql-hackers

From Asim R P
Subject Re: Shared buffer access rule violations?
Date
Msg-id CANXE4TeGLrNs1OauDzKzXrgwZKRNzxV4FBx4LA=-E6OKv9f0GA@mail.gmail.com
Whole thread Raw
In response to Re: Shared buffer access rule violations?  (Peter Geoghegan <pg@bowt.ie>)
Responses Re: Shared buffer access rule violations?
List pgsql-hackers
On Tue, Aug 7, 2018 at 7:00 PM, Peter Geoghegan <pg@bowt.ie> wrote:
>
> I wonder if it would be a better idea to enable Valgrind's memcheck to
> mark buffers as read-only or read-write. We've considered doing
> something like that for years, but for whatever reason nobody followed
> through.

Basic question: how do you mark buffers as read-only using memcheck
tool?  Running installcheck with valgrind didn't uncover any errors:

valgrind --trace-children=yes pg_ctl -D datadir start
make installcheck-parallel

Asim & David


pgsql-hackers by date:

Previous
From: Peter Geoghegan
Date:
Subject: Re: [WIP] [B-Tree] Retail IndexTuple deletion
Next
From: Andres Freund
Date:
Subject: Re: Why do we expand tuples in execMain.c?