Re: what's going on with lapwing? - Mailing list pgsql-hackers

From Tom Lane
Subject Re: what's going on with lapwing?
Date
Msg-id 704850.1741281767@sss.pgh.pa.us
Whole thread Raw
In response to Re: what's going on with lapwing?  (Andrew Dunstan <andrew@dunslane.net>)
Responses Re: what's going on with lapwing?
List pgsql-hackers
Andrew Dunstan <andrew@dunslane.net> writes:
> On 2025-03-06 Th 10:45 AM, Robert Haas wrote:
>> By the way, is there a particular reason why we're keeping Debian 7
>> coverage in the buildfarm? I don't want to be in a huge rush to kill
>> platforms people still care about, but it was pointed out to me
>> off-list that this is quite an old release -- it seems Debian 7 was
>> first released in 2013, last released in 2016, EOL in 2018. I assume
>> that not too many people are going to install a PostgreSQL release
>> that comes out in 2025 on an OS that's been EOL for 7 years (or 12
>> years if the BF page is correct that this is actually Debian 7.0).

I don't think that's the way to think about old buildfarm members.
Sure, nobody is very likely to be putting PG 18 on a Debian 7 box,
but the odds are much higher that they might have PG 13 on it and
wish to update to 13.latest.  So what you need to compare OS EOL
dates to is not current development but our oldest supported branch.

Having said that, PG 13 came out in 2020, so yeah it'd be reasonable
to retire Debian 7 buildfarm animals now.  But the gap isn't nearly
as large as you make it sound.

> We do have a project at EDB at fill in certain gaps in buildfarm 
> coverage, so maybe we can reduce the incidence of such accidents.

+1

            regards, tom lane



pgsql-hackers by date:

Previous
From: Christoph Berg
Date:
Subject: Re: zstd failing on mipsel (PG 15.12, pg_verifybackup/t/010_client_untar.pl)
Next
From: Jelte Fennema-Nio
Date:
Subject: Re: Next commitfest app release is planned for March 18th