Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1vM8iF-00201i-0P for pgsql-general@arkaria.postgresql.org; Thu, 20 Nov 2025 17:44:55 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.96) (envelope-from ) id 1vM8iC-003Ezv-04 for pgsql-general@arkaria.postgresql.org; Thu, 20 Nov 2025 17:44:52 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1vM4EM-001fJ0-2H for pgsql-general@lists.postgresql.org; Thu, 20 Nov 2025 12:57:47 +0000 Received: from mail-yw1-x112d.google.com ([2607:f8b0:4864:20::112d]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.96) (envelope-from ) id 1vM4EK-000Wej-1V for pgsql-general@lists.postgresql.org; Thu, 20 Nov 2025 12:57:46 +0000 Received: by mail-yw1-x112d.google.com with SMTP id 00721157ae682-7866375e943so6862697b3.0 for ; Thu, 20 Nov 2025 04:57:45 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=20230601; t=1763643464; x=1764248264; darn=lists.postgresql.org; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:from:to:cc:subject:date :message-id:reply-to; bh=mBxd45N3PiZqQq7/6M3GV1D453lUYvWZroFS12y6Bb0=; b=M5umeceiY8o1mFcnrvvAaSRQhPmu0Xds2tXU+TiQkQsimvOD0nWMpVXblg/HDVsdRW zm05tMO6mBjSawnuJjN2dhtipBcLzhhdR2n/wyCIaJc7aaj/WdEjOWXUayLkCiLHZZlE gXJg5mfRM7/y0U1FqaV0faLRkBzWKjFAMV8e/3baKq1i52n1Mt0MK7zvmTRVpvsK1ytQ JbLK6TNSV+ak806QsKQoK1WeEX3XahpywGEud4aVezjIk1oAiEI5Vb3eCzf4evnp4fZh mJ4VLGT+B9XMXXwvWmr9sX3Z3PaDsTUjmEq0LGghY7SOE6DSxcgEVszsTMm0aMgu/FgW wSNA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1763643464; x=1764248264; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:x-gm-gg:x-gm-message-state:from :to:cc:subject:date:message-id:reply-to; bh=mBxd45N3PiZqQq7/6M3GV1D453lUYvWZroFS12y6Bb0=; b=ftfBG6zgHPNHs+YorSpByw9sE3oSOdbVvubol/Bih2oLVKmpZA8cJE2zo3CVR0jNC0 aZFFMOlN8H0tFRdgCv3iIK1p7v65V8Vve1xeS6XlxXpjbkroYuTfVG6vUv9I2gyleKw/ OSe2F8KHqpYkVgq7N1vLnHQueSyC+o4CX0lFRLc+3QzVCGWWB+BPFqEk+Y4TLmuWp3kM xWmrV0sGzU1f52WnrEkRGltFKEFH8hrgzbYpuoKyg/ssf/YV5VVofpj/f6pFmPWxviRd sbHyQMw0c2mB5caVoW1YBS32/1RW4iw4firoZgREoA32I1zResK2bxDVWId63we2/9yj PFLg== X-Gm-Message-State: AOJu0YwsUOg5bVVWOFkGS8fnthsYKZkF+/S3Oc95boAmXywPmtkLx0wW Dh5WeyxKm9yht9cNFQRRfS4d80bIeEV/J5DeMdYcwS0Olwrx44wwakn5JObYV+KQ+/gZ4xQVLqa 2dW56Z2cNeIu2VNDampf2BKutaKKyXh0= X-Gm-Gg: ASbGncsbe/744IRzeT1z96ID7Fn7lK3WerX9IEN2FnRixMb/c6LDXBATOXGF2V0y/3q nLYGAU3+Zh/XMtcNpJFjpYPT6t0Tfr5LuXEeLKUpBdupcE2hZzgEzHdO7IMQbLla2PyTmC1Ndbi nM4nryMXLY+TxjsAvbkQQiHGykVoknBxWBb077h/75ovyX0bDrklpNMptcKyVJE3whvYBI8t9Rl aLTwtK1C9/52aFhVCs4llX4AExbi2zbbJnSaLdu/W7RQGwiahLodg9okzfdFCORqNoj87wk X-Google-Smtp-Source: AGHT+IGIrgQnOCC1Jg28N7aucakfkdo0VZbXNI8V43CjwUxsvoBHOrqm29eRxT/JNyBEaH7HSZtBkKv17byLHmSjrYc= X-Received: by 2002:a05:690e:d48:b0:641:f5bc:68e2 with SMTP id 956f58d0204a3-642f7a89eb2mr2089535d50.79.1763643464267; Thu, 20 Nov 2025 04:57:44 -0800 (PST) MIME-Version: 1.0 References: <202511201242.4pht5cyc33ex@alvherre.pgsql> In-Reply-To: <202511201242.4pht5cyc33ex@alvherre.pgsql> From: Hu Bert Date: Thu, 20 Nov 2025 13:57:33 +0100 X-Gm-Features: AWmQ_bkgR7HoBDOAhn77Q1PonqA7mZm4QKHTfVYi0mpkPAFPoC_WD_VV_y_PN3M Message-ID: Subject: Re: postgresql-17 on debian bookworm - directories missing To: =?UTF-8?Q?=C3=81lvaro_Herrera?= Cc: pgsql-general@lists.postgresql.org Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Hi =C3=81lvaro, 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=3D/etc/postgresql/14/main/postgresql.conf" --new-options "-c config_file=3D/etc/postgresql/16/main/postgresql.conf" --old-bindir=3D/usr/lib/postgresql/14/bin/ --new-bindir=3D/usr/lib/postgresql/16/bin/ --old-datadir=3D/var/lib/postgresql/14/main --new-datadir=3D/var/lib/postgresql/16/main --old-port=3D5432 --new-port=3D5433 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 =C3=81lvaro Herrera : > > 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. > > -- > =C3=81lvaro Herrera 48=C2=B001'N 7=C2=B057'E =E2=80=94 ht= tps://www.EnterpriseDB.com/