public inbox for [email protected]  

help / color / mirror / Atom feed

Change in behavior when installing an additional PostgreSQL major version
2+ messages / 2 participants
[nested] [flat]

* Change in behavior when installing an additional PostgreSQL major version
@ 2025-02-24 14:51 Schmid Andreas <[email protected]>
  2025-02-24 15:19 ` Re: Change in behavior when installing an additional PostgreSQL major version Christoph Berg <[email protected]>
  0 siblings, 1 reply; 2+ messages in thread

From: Schmid Andreas @ 2025-02-24 14:51 UTC (permalink / raw)
  To: [email protected] <[email protected]>

Hi

I've noticed that the commit https://salsa.debian.org/postgresql/postgresql-common/-/commit/d9139f7777a42a39b5b6fabbffc9f020fad4d... has introduced a change in behavior when installing an additional PostgreSQL major version alongside any other already installed major version. (I originally asked on pgsql-general: https://www.postgresql.org/message-id/a17b7bcaf49848e5a1ec722ddfb3ba6e%40bd.so.ch)

So far, my PostgreSQL installation script relied on a new cluster being created in any case. 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?

Thanks a lot,
Andy



Attachments:

  [application/pkcs7-signature] smime.p7s (7.3K, 3-smime.p7s)
  download

^ permalink  raw  reply  [nested|flat] 2+ messages in thread

* Re: Change in behavior when installing an additional PostgreSQL major version
  2025-02-24 14:51 Change in behavior when installing an additional PostgreSQL major version Schmid Andreas <[email protected]>
@ 2025-02-24 15:19 ` Christoph Berg <[email protected]>
  0 siblings, 0 replies; 2+ messages in thread

From: Christoph Berg @ 2025-02-24 15:19 UTC (permalink / raw)
  To: Schmid Andreas <[email protected]>; +Cc: [email protected] <[email protected]>

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






^ permalink  raw  reply  [nested|flat] 2+ messages in thread

end of thread, other threads:[~2025-02-24 15:19 UTC | newest]

Thread overview: 2+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2025-02-24 14:51 Change in behavior when installing an additional PostgreSQL major version Schmid Andreas <[email protected]>
2025-02-24 15:19 ` Christoph Berg <[email protected]>

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