Re: sys_siglist[] is causing us trouble again
Andrew Dunstan <andrew.dunstan@2ndquadrant.com>
From: Andrew Dunstan <andrew.dunstan@2ndquadrant.com>
To: PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Date: 2020-07-16T13:34:19Z
Lists: pgsql-hackers
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
Commits
-
Replace use of sys_siglist[] with strsignal().
- d61dcccaf926 9.5.23 landed
- 9e043d93c843 9.6.19 landed
- c6d43ffab3c0 11.9 landed
- 0140dec18019 10.14 landed