From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Thomas Munro <thomas(dot)munro(at)gmail(dot)com> |
Cc: | Andres Freund <andres(at)anarazel(dot)de>, pgsql-hackers(at)lists(dot)postgresql(dot)org, Xing Guo <higuoxing(at)gmail(dot)com>, Devrim Gündüz <devrim(at)gunduz(dot)org>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Guiding principle for dropping LLVM versions? |
Date: | 2023-10-25 06:11:58 |
Message-ID: | 914716.1698214318@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Thomas Munro <thomas(dot)munro(at)gmail(dot)com> writes:
> Here are some systematic rules I'd like to propose to anchor this
> stuff to reality and avoid future doubt and litigation:
> 1. Build farm animals testing LLVM determine the set of OSes and LLVM
> versions we consider.
> 2. We exclude OSes that will be out of full vendor support when a
> release ships.
> 3. We exclude OSes that don't bless an LLVM release (eg macOS running
> an arbitrarily picked version), and animals running only to cover
> ancient LLVM compiled from source for coverage (Andres's sid
> menagerie).
Seems generally reasonable. Maybe rephrase 3 as "We consider only
an OS release's default LLVM version"? Or a bit more forgivingly,
"... only LLVM versions available from the OS vendor"? Also,
what's an OS vendor? You rejected macOS which is fine, but
I think the packages available from MacPorts or Homebrew should
be considered.
You could imagine somebody trying to game the system by standing up a
buildfarm animal running some really arbitrary combination of versions
--- but what would be the point? I think we can deal with that
when/if it happens. But "macOS running an LLVM version available
from MacPorts" doesn't seem arbitrary.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Amul Sul | 2023-10-25 06:12:35 | Re: ALTER COLUMN ... SET EXPRESSION to alter stored generated column's expression |
Previous Message | Amit Kapila | 2023-10-25 06:09:07 | Re: [PoC] pg_upgrade: allow to upgrade publisher node |