Valgrind and shared_buffers (Was: Restore-reliability mode) - Mailing list pgsql-hackers

From Peter Geoghegan
Subject Valgrind and shared_buffers (Was: Restore-reliability mode)
Date
Msg-id CAM3SWZR3XB5Hw_bkHkAKm_HTQRMPRzPH4bKFicPUFriZiSWa0w@mail.gmail.com
Whole thread Raw
Responses Re: Valgrind and shared_buffers (Was: Restore-reliability mode)  (Alvaro Herrera <alvherre@2ndquadrant.com>)
List pgsql-hackers
On Mon, Jul 27, 2015 at 7:12 AM, Alvaro Herrera
<alvherre@2ndquadrant.com> wrote:
> I only tried a few tests, for lack of time, and it didn't produce any.
> (To verify that the whole thing was working properly, I reduced the
> range of memory made available during PinBuffer and that resulted in a
> crash immediately).  I am not really familiar with valgrind TBH and just
> copied a recipe to run postmaster under it, so if someone with more
> valgrind-fu could verify this, it would be great.
>
>
> This part:
>
>> > > >     Under CLOBBER_FREED_MEMORY, wipe a shared buffer when its
>> > > >     global pin count falls to zero.
>
> can be done without any valgrind, I think.  Any takers?

It seems like this didn't go anywhere. Any chance that you'll find the
time to work on this soon?

-- 
Peter Geoghegan



pgsql-hackers by date:

Previous
From: Bill Moran
Date:
Subject: Re: RFC/WIP: adding new configuration options to TOAST
Next
From: Ashutosh Bapat
Date:
Subject: Re: Getting sorted data from foreign server