From: | Schmid Andreas <Andreas(dot)Schmid(at)bd(dot)so(dot)ch> |
---|---|
To: | "pgsql-general(at)lists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org> |
Subject: | PGDG PostgreSQL Debian package: Question on conditions for creation of new cluster |
Date: | 2025-02-19 08:45:53 |
Message-ID: | a17b7bcaf49848e5a1ec722ddfb3ba6e@bd.so.ch |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Hi
I'm trying to install the postgresql-17 Debian package from PGDG apt repo alongside an already existing PostgreSQL 16 installation. So there is already a PostgreSQL 16 cluster on my machine (which I want to upgrade to version 17 using the pg_upgrade command later on).
If I'm not wrong, the PostgreSQL packages used to automatically create a new cluster during installation, even if there already was an older cluster present. (Using a different port in this case.) But this doesn't happen with the 17.3 package. Does anyone know if this behavior has changed? Or anyone can explain on which conditions a new cluster is created and when not?
There was a now closed discussion on this topic on Stack Overflow: https://stackoverflow.com/questions/79441161/postgres-17-3-installation-no-longer-creates-a-new-cluster. Of course, I will create the additional cluster using pg_createcluster if this is the way to go. The point is that I'm installing PostgreSQL using an Ansible script, and pg_createcluster was not needed until now. So before I update my script, I hope to get some more information about the behavior of the PostgreSQL packages regarding automatic cluster creation.
Thanks a lot,
Andy
From | Date | Subject | |
---|---|---|---|
Next Message | Laurenz Albe | 2025-02-19 09:50:27 | Re: PGDG PostgreSQL Debian package: Question on conditions for creation of new cluster |
Previous Message | Greg Sabino Mullane | 2025-02-19 00:10:06 | Re: How to select avg(select max(something) from ...) |