| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | Andrew Dunstan <andrew(at)dunslane(dot)net>, Julien Rouhaud <rjuju123(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Andrew Dunstan <adunstan(at)postgresql(dot)org>, pgbuildfarm(at)rjuju(dot)net |
| Subject: | Re: what's going on with lapwing? |
| Date: | 2025-03-06 19:13:40 |
| Message-ID: | 717343.1741288420@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Robert Haas <robertmhaas(at)gmail(dot)com> writes:
> On Thu, Mar 6, 2025 at 1:07 PM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2025-03-06 19:15:03 | Re: ZStandard (with dictionaries) compression support for TOAST compression |
| Previous Message | Robert Haas | 2025-03-06 19:12:40 | Re: Showing primitive index scan count in EXPLAIN ANALYZE (for skip scan and SAOP scans) |