Re: Restore-reliability mode
Alvaro Herrera <alvherre@2ndquadrant.com>
From: Alvaro Herrera <alvherre@2ndquadrant.com>
To: Noah Misch <noah@leadboat.com>
Cc: 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:57:56Z
Lists: pgsql-hackers
Noah Misch wrote:
> - Add buildfarm members. This entails reporting any bugs that prevent an
> initial passing run. Once you have a passing run, schedule regular runs.
> Examples of useful additions:
> - "./configure ac_cv_func_getopt_long=no, ac_cv_func_snprintf=no ..." to
> enable all the replacement code regardless of the current platform's need
> for it. This helps distinguish "Windows bug" from "replacement code bug."
> - --disable-integer-datetimes, --disable-float8-byval, disable-float4-byval,
> --disable-spinlocks, --disable-atomics, disable-thread-safety,
> --disable-largefile, #define RANDOMIZE_ALLOCATED_MEMORY
#define RELCACHE_FORCE_RELEASE + #define CLOBBER_FREED_MEMORY
--
Á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