From: Andrew Dunstan <andrew.dunstan@2ndquadrant.com>
To: PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Subject: Re: sys_siglist[] is causing us trouble again
Date: Thu, 16 Jul 2020 09:34:19 -0400
Message-ID: <938ea3ff-64b7-60f4-ee01-da40dde97d79@2ndQuadrant.com> (raw)
In-Reply-To: <3181175.1594856198@sss.pgh.pa.us>
References: <3179114.1594853308@sss.pgh.pa.us>
<CA+hUKGLJJjGz+qi+t7qDkFYO2=4a4YECXucH8WZoein8LPbeAA@mail.gmail.com>
<3181175.1594856198@sss.pgh.pa.us>
On 7/15/20 7:36 PM, Tom Lane wrote:
> I guess rawhide is the RH thing that tracks the bleeding edge?
> Yup. Possibly we should recommend that buildfarm owners running on
> non-stable platforms disable autoconf result caching --- I believe
> that's "use_accache => undef" in the configuration file.
>
> Alternatively, maybe it'd be bright for the buildfarm script to
> discard that cache after any failure (or at least configure or
> build failures).
Yeah, these lines will be added to the upcoming client code release in
run_build.pl Search for 'obsolete' and you'll find where to put it if
you want to be ahead of the curve.
my $last_stage = get_last_stage() || "";
$obsolete ||=
$last_stage =~ /^(Make|Configure|Contrib|.*-build)$/;
cheers
andrew
--
Andrew Dunstan https://www.2ndQuadrant.com
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-hackers@postgresql.org
Cc: andrew.dunstan@2ndquadrant.com, pgsql-hackers@lists.postgresql.org
Subject: Re: sys_siglist[] is causing us trouble again
In-Reply-To: <938ea3ff-64b7-60f4-ee01-da40dde97d79@2ndQuadrant.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox