MIME-Version: 1.0
Date: Sun, 01 Sep 2024 12:32:43 +1000
From: Justin Clift <justin@postgresql.org>
To: "Peter J. Holzer" <hjp-pgsql@hjp.at>
Cc: pgsql-general@postgresql.org
Subject: Re: Upgrade Ubuntu 22 -> 24 may break PostgreSQL
In-Reply-To: <20240831165445.7kqb4ezzghaysbc7@hjp.at>
References: <20240831165445.7kqb4ezzghaysbc7@hjp.at>
User-Agent: Roundcube Webmail/1.4.15
Message-ID: <f3c2187d68ec125c4f2ede69c0d6c49d@postgresql.org>
Content-Type: text/plain; charset=US-ASCII;
 format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <https://www.postgresql.org/message-id/f3c2187d68ec125c4f2ede69c0d6c49d%40postgresql.org>
Precedence: bulk

On 2024-09-01 02:54, Peter J. Holzer wrote:
> 'Tis the season again.
> 
> Ubuntu 24.04.1 has just been released, so many Ubuntu LTS users will 
> now
> be prompted to upgrade from 22.04 to 24.04.
> 
> A word of warning to those who use Postgresql from the Ubuntu repo (not
> PGDG):
> 
> As usual, a newer Ubuntu version comes with a newer Postgres version 
> (16
> instead of 14). Also as usual, I got a message during the upgrade that
> Postgres 14 is obsolete,. but the binaries have been left installed and
> I should upgrade to Postgres 16 manually ASAP.

It'd *technically* be possible to automatically run an upgrade of the
PostgreSQL repository (via scripting?) at launch time, though just 
blindly
doing it for everyone would be a *major* change of behaviour.

Some people would likely love it, while others would be horrified (etc).

That being said, if we announce it ahead of time as a feature of a major
release (ie PG 18 or something), and if we have a clear way to not
automatically upgrade (a variable in postgresql.conf?), then we might be
able to solve this problem ~permanently.

We'd also need to figure out how to handle (say) rebuilding of indexes
that need updating between major versions and stuff like that.

Thoughts?

Regards and best wishes,

Justin Clift