Hi Álvaro, interesting - about one and a half year ago i upgraded postgresql from 14 to 16 - installed the v16 packages, and both versions and two clusters were running.
upgrade: /usr/lib/postgresql/16/bin/pg_upgrade --link --old-options "-c config_file=/etc/postgresql/14/main/postgresql.conf" --new-options "-c config_file=/etc/postgresql/16/main/postgresql.conf" --old-bindir=/usr/lib/postgresql/14/bin/ --new-bindir=/usr/lib/postgresql/16/bin/ --old-datadir=/var/lib/postgresql/14/main --new-datadir=/var/lib/postgresql/16/main --old-port=5432 --new-port=5433 So that must've changed in the past. However... so i have 2 options: - create a v17 cluster and run pg_upgrade or - run pg_upgradecluster Have to check the 2nd command :-) Thx, Hubert Am Do., 20. Nov. 2025 um 13:46 Uhr schrieb Álvaro Herrera <[email protected]>: > > On 2025-Nov-20, Hu Bert wrote: > > > Hi there, > > i have a debian bookworm with postgresql-16 installed, from postgresql > > repository. I wanted to install postgresql-17 and then do a an inplace > > upgrade via pg_upgrade. > > > > Install: apt install postgresql-17 postgresql-17-postgis-3 > > postgresql-17-postgis-3-scripts postgresql-client-17 > > > > But after the installation there's no v17 cluster: > > I think this is expected. The Debian packages create a cluster when you > install the server packages only if you don't already have a cluster. > Here it's clearly that you do have one, so a new one isn't created. You > could create one yourself with pg_createcluster. However, if what you > want to do is to upgrade the 16 one, then I think you don't need to > create a new one, but instead use pg_upgradecluster which will create > one for you. > > -- > Álvaro Herrera 48°01'N 7°57'E — https://www.EnterpriseDB.com/
