Re: what's going on with lapwing?
Tom Lane <tgl@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Robert Haas <robertmhaas@gmail.com>
Cc: Andrew Dunstan <andrew@dunslane.net>, Julien Rouhaud <rjuju123@gmail.com>,
PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>,
Andrew Dunstan <adunstan@postgresql.org>, pgbuildfarm@rjuju.net
Date: 2025-03-06T19:13:40Z
Lists: pgsql-hackers
Robert Haas <robertmhaas@gmail.com> writes: > On Thu, Mar 6, 2025 at 1:07 PM Tom Lane <tgl@sss.pgh.pa.us> wrote: >> Maybe invent a build-farm.conf option like "newest_branch_to_build"? > Yes, that would be nice. I also think we should mandate the use of > that option for OS versions that are EOL for more than X years, for > some to-be-determined value of X, like maybe 3 or something. It's hard to "mandate" anything in a distributed project like this. I don't really see a need to either, at least for cases where an old animal isn't causing us extra work. When it does, though, it'd be nice to be able to decide "we're not gonna support that OS version beyond PG nn", and then have a simple recipe to give the BF owner that's less drastic than "shut it down". regards, tom lane
Commits
-
Revert workarounds for -Wmissing-braces false positives on old GCC
- 618c64ffd396 18.0 landed
-
Convert sepgsql tests to TAP
- aeb8ea361a0a 18.0 cited