Re: Shared buffer access rule violations?

From: Asim R P <apraveen(at)pivotal(dot)io>
To: Peter Geoghegan <pg(at)bowt(dot)ie>
Cc: PostgreSQL mailing lists <pgsql-hackers(at)postgresql(dot)org>, David Kimura <dkimura(at)pivotal(dot)io>
Subject: Re: Shared buffer access rule violations?
Date: 2018-08-09 00:59:04
Message-ID: CANXE4TeGLrNs1OauDzKzXrgwZKRNzxV4FBx4LA=-E6OKv9f0GA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, Aug 7, 2018 at 7:00 PM, Peter Geoghegan <pg(at)bowt(dot)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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Andres Freund 2018-08-09 01:15:39 Re: Why do we expand tuples in execMain.c?
Previous Message Peter Geoghegan 2018-08-09 00:19:51 Re: [WIP] [B-Tree] Retail IndexTuple deletion