public inbox for [email protected]  

help / color / mirror / Atom feed

From: Jeremy Schneider <[email protected]>
To: Christoph Berg <[email protected]>
Cc: [email protected]
Subject: Re: pg18 patch: separate package for llvm/jit
Date: Sat, 1 Mar 2025 16:51:49 -0800
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>
	<[email protected]>

On Fri, 28 Feb 2025 16:02:42 +0100
Christoph Berg <[email protected]> wrote:

> Re: Jeremy Schneider
> > I would like to propose this change for Postgres 18.
> 
> Hi,
> 
> I committed a change to the PG18 packaging that implements that split.
> The new package is called postgresql-18-jit.

wow!! i did not expect this 🙂

> There is more work to do on each of the extension packages currently
> depending on "postgresql-18-jit-llvm (= llvmversion)", that needs to
> be converted to "Breaks: postgresql-18-jit-llvm (<< llvmversion)".
> (This is also the reason the jit package is not called like that
> because the version number there is not the PG version number.)
> 
> This will likely happen when extensions are moved to PG18 in
> September.

i'll take a look and learn a bit more about it.

one question - the commit message says "Closes: #927182" and i'm
curious what that number is a reference to? It doesn't seem to be an
issue or PR that I found on salsa.debian.org but maybe I haven't looked
in the right place yet.


> I'm unsure if the split should be backported to PG 17 and earlier
> since it will affect production systems in some way.

FWIW, i'm not a debian packaging expert but i was assuming this would
not be backported. i don't think we'd want existing installation
scripts to change behavior on a postgres minor update (eg. newly
provisioned servers no longer getting JIT installed by default, when
previously provisioned servers of the same major version have it)

-Jeremy

view thread (4+ messages)  latest in thread

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: [email protected]
  Cc: [email protected], [email protected], [email protected]
  Subject: Re: pg18 patch: separate package for llvm/jit
  In-Reply-To: <[email protected]>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox