Re: Restore-reliability mode
Alvaro Herrera <alvherre@2ndquadrant.com>
From: Alvaro Herrera <alvherre@2ndquadrant.com>
To: Peter Geoghegan <pg@heroku.com>
Cc: Noah Misch <noah@leadboat.com>, Simon Riggs <simon@2ndquadrant.com>,
Bruce Momjian <bruce@momjian.us>, Andres Freund <andres@anarazel.de>,
Robert Haas <robertmhaas@gmail.com>, Tom Lane <tgl@sss.pgh.pa.us>,
Stephen Frost <sfrost@snowman.net>, Magnus Hagander <magnus@hagander.net>,
"pgsql-hackers@postgresql.org" <pgsql-hackers@postgresql.org>,
pgsql-core <pgsql-core@postgresql.org>
Date: 2015-07-23T19:53:49Z
Lists: pgsql-hackers
Attachments
- 0001-add-valgrind-calls.patch (text/x-diff) patch 0001
Peter Geoghegan wrote: > On Sat, Jun 6, 2015 at 12:58 PM, Noah Misch <noah@leadboat.com> wrote: > > - Call VALGRIND_MAKE_MEM_NOACCESS() on a shared buffer when its local pin > > count falls to zero. Under CLOBBER_FREED_MEMORY, wipe a shared buffer > > when its global pin count falls to zero. > > Did a patch for this ever materialize? I think the first part would be something like the attached. -- Álvaro Herrera http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
Commits
-
Add Valgrind buffer access instrumentation.
- 1e0dfd166b3f 14.0 landed
-
Fix wrong merge resolution making pg_receivexlog fail in 9.2.
- 6b700301c36e 9.2.11 cited