| From: | Schmid Andreas <Andreas(dot)Schmid(at)bd(dot)so(dot)ch> |
|---|---|
| To: | "pgsql-pkg-debian(at)lists(dot)postgresql(dot)org" <pgsql-pkg-debian(at)lists(dot)postgresql(dot)org> |
| Subject: | Change in behavior when installing an additional PostgreSQL major version |
| Date: | 2025-02-24 14:51:07 |
| Message-ID: | e8c0e0e43cf0458fa3a021dd0cb398c8@bd.so.ch |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-pkg-debian |
Hi
I've noticed that the commit https://salsa.debian.org/postgresql/postgresql-common/-/commit/d9139f7777a42a39b5b6fabbffc9f020fad4dce5 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Christoph Berg | 2025-02-24 15:19:39 | Re: Change in behavior when installing an additional PostgreSQL major version |
| Previous Message | Jeremy Schneider | 2025-02-24 01:02:05 | notice from apt update (noble/i386) |