| From: | Andres Freund <andres(at)anarazel(dot)de> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | pgsql-hackers(at)lists(dot)postgresql(dot)org, Thomas Munro <thomas(dot)munro(at)gmail(dot)com>, Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr> |
| Subject: | Re: Latest LLVM breaks our code again |
| Date: | 2022-02-01 20:02:44 |
| Message-ID: | 20220201200244.em2frrvcq2hx35ei@alap3.anarazel.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi,
On 2022-01-30 21:38:16 -0500, Tom Lane wrote:
> Speaking of buildfarm breakage, seawasp has been failing for the
> past several days. It looks like bleeding-edge LLVM has again
> changed some APIs we depend on. First failure is here:
I'm doubtful that tracking development branches of LLVM is a good
investment. Their development model is to do changes in-tree much more than we
do. Adjusting to API changes the moment they're made will often end up with
further changes to the same / related lines. Once they open the relevant
release-NN branch, it's a different story.
Maybe it'd make sense to disable --with-llvm on seawasp and have a separate
animal that tracks the newest release branch?
Greetings,
Andres Freund
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Stephen Frost | 2022-02-01 20:12:28 | Re: Support for NSS as a libpq TLS backend |
| Previous Message | David Rowley | 2022-02-01 20:02:38 | Re: Why is INSERT-driven autovacuuming based on pg_class.reltuples? |