Re: Requiring LLVM 14+ in PostgreSQL 18

From: Peter Eisentraut <peter(at)eisentraut(dot)org>
To: Thomas Munro <thomas(dot)munro(at)gmail(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Requiring LLVM 14+ in PostgreSQL 18
Date: 2024-05-12 14:32:59
Message-ID: 5255e75e-5a66-41ac-99d3-1998283b86e6@eisentraut.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 24.04.24 01:43, Thomas Munro wrote:
> Rebased over ca89db5f.

These patches look fine to me. The new cut-off makes sense, and it does
save quite a bit of code. We do need to get the Cirrus CI Debian images
updated first, as you had already written.

As part of this patch, you also sneak in support for LLVM 18
(llvm-config-18, clang-18 in configure). Should this be a separate patch?

And as I'm looking up how this was previously handled, I notice that
this list of clang-NN versions was last updated equally sneakily as part
of your patch to trim off LLVM <10 (820b5af73dc). I wonder if the
original intention of that configure code was that maintaining the
versioned list above clang-7/llvm-config-7 was not needed, because the
unversioning programs could be used, or maybe because pkg-config could
be used. It would be nice if we could get rid of having to update that.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Dmitry Koval 2024-05-12 14:43:40 Re: Add SPLIT PARTITION/MERGE PARTITIONS commands
Previous Message Matthias van de Meent 2024-05-12 13:18:44 Re: Comments about TLS (no SSLRequest) and ALPN