Re: Change in behavior when installing an additional PostgreSQL major version

From: Christoph Berg <myon(at)debian(dot)org>
To: Schmid Andreas <Andreas(dot)Schmid(at)bd(dot)so(dot)ch>
Cc: "pgsql-pkg-debian(at)lists(dot)postgresql(dot)org" <pgsql-pkg-debian(at)lists(dot)postgresql(dot)org>
Subject: Re: Change in behavior when installing an additional PostgreSQL major version
Date: 2025-02-24 15:19:39
Message-ID: Z7yOC-qHhrhxjUoA@msg.df7cb.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-pkg-debian

Re: Schmid Andreas
> Now, I had to add a separate pg_createcluster command, which basically wasn't a big deal. However, as I had to do quite some research to understand why all of a sudden my script didn't work anymore, maybe you can give some background about the reasons that led to this change?

Hi,

the old behavior wasn't practical for the majority of users. To
upgrade, you had to install the new PG package and then run
"pg_dropcluster" as the first command. That was weird and possibly
dangerous.

Christoph

In response to

Browse pgsql-pkg-debian by date

  From Date Subject
Next Message Jeremy Schneider 2025-02-24 21:48:29 pg18 patch: separate package for llvm/jit
Previous Message Schmid Andreas 2025-02-24 14:51:07 Change in behavior when installing an additional PostgreSQL major version