Re: Restore-reliability mode

From: Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>
To: Noah Misch <noah(at)leadboat(dot)com>
Cc: Simon Riggs <simon(at)2ndQuadrant(dot)com>, Bruce Momjian <bruce(at)momjian(dot)us>, Andres Freund <andres(at)anarazel(dot)de>, Robert Haas <robertmhaas(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Stephen Frost <sfrost(at)snowman(dot)net>, Magnus Hagander <magnus(at)hagander(dot)net>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>, pgsql-core <pgsql-core(at)postgresql(dot)org>
Subject: Re: Restore-reliability mode
Date: 2015-07-23 19:57:56
Message-ID: 20150723195756.GX5596@postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
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

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Josh Berkus 2015-07-23 19:58:41 Re: Autonomous Transaction is back
Previous Message Alvaro Herrera 2015-07-23 19:53:49 Re: Restore-reliability mode