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.94.2) (envelope-from ) id 1tkgiw-005yo8-6J for pgsql-general@arkaria.postgresql.org; Wed, 19 Feb 2025 09:50:34 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1tkgiu-006USl-7e for pgsql-general@arkaria.postgresql.org; Wed, 19 Feb 2025 09:50:32 +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.94.2) (envelope-from ) id 1tkgit-006USZ-SA for pgsql-general@lists.postgresql.org; Wed, 19 Feb 2025 09:50:32 +0000 Received: from mail-ed1-x52d.google.com ([2a00:1450:4864:20::52d]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.96) (envelope-from ) id 1tkgir-001ger-38 for pgsql-general@lists.postgresql.org; Wed, 19 Feb 2025 09:50:31 +0000 Received: by mail-ed1-x52d.google.com with SMTP id 4fb4d7f45d1cf-5ded1395213so10612588a12.2 for ; Wed, 19 Feb 2025 01:50:29 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cybertec.at; s=google; t=1739958628; x=1740563428; darn=lists.postgresql.org; h=mime-version:user-agent:references:in-reply-to:date:to:from:subject :message-id:from:to:cc:subject:date:message-id:reply-to; bh=SbAJOx4ZPyDjTlaBoOn/g1qwDVh5o0ir45COXAI12tY=; b=BOmwM0b60Jqn3fLkUzS54GUFc06xRUwqZBiEgDVqt3VWy8NCNOFBzJkQz868Te21bV Z4RGlqWeB3IR1+BOo48dCQQb9+m/X7seGEKldelj/a/2V2TIxKMWf67gtpXuKtj1rmNM q39+wi4U1HVIIRhYHlS0sgBLpci5cLhKOfSZV+Axo5JBul8tLM1lyent3wz26cjwnZq5 GCn297vq+qLPHsk2+2y/+XHBchWWFHhBwwz8TT2arpo7hTEFqbONZPUOfdJPg1fsiuKM BRCniK2QrZKtlGYrYB8aXcv4rRL2K6FBQzsPSrQRRCUf8oPTRjlEzD8u27TwnMlG7pD5 Dvcg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1739958628; x=1740563428; h=mime-version:user-agent:references:in-reply-to:date:to:from:subject :message-id:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=SbAJOx4ZPyDjTlaBoOn/g1qwDVh5o0ir45COXAI12tY=; b=iR7mFxhZSxSxLxqrcPrcHC7S4HaSuY70YExbX/I0Sd8K+LjVStoGBu/aL8MZ8bbF9I oMlKIcy71QCjbdNToNKeif2T61To3RP9eUvGQs6108bjXK+shrHCyvy+e9hgzASRxjUZ sliKd++gK0n/ASWjhkYVmYibb39Hd9Urq3eEhL55SUsrxVLjsq/C2vLKsbmF9lY4NqVs MaI8R3y2+T+gvvkSYwPSQH4DS+iNktFiFN5Kg5ZC79QgH/hLmYYp6z/wxR19BEVBjM4Y n1JSsMNBFjsDpKNqXPYn+1sIqQrs4/I/b9S9FVEKE+2d6b7c8A5ibp62lhhBT/XYq4rm zUuQ== X-Forwarded-Encrypted: i=1; AJvYcCXoh7CYmeDjSGcPD/z2jG4kx3Kp/kvZVKz1dprSbj4KcXeEmk/40wgUB+6gyXf35FCH0EbVli3HgN2zdou+@lists.postgresql.org X-Gm-Message-State: AOJu0YwXjeNeesy5uKHPqnpchozVK27FEGaTkPc/6XkEejMOkOpF9LRN 1uqNgDoP+yZm8PWSa2HQGjphnzlf//yLuW3I0oQ2OlaxGGQ9JwsW/WTaUbu81pPaA8cz70EU//N nFbQDEYFkzEFfYhP2sDLcsKysY8PUvcvbb/DzAy5EX8Sji/Fzf192//8JgjST0tO3 X-Gm-Gg: ASbGncug7D6u9d/Y1AHXkwibEHd3HeBULmiSzVyd7zGjBC1dvGca6cCh2aWkSY56hhb 808Gp4vGvVd6XBNdvQ1DoJZMWfBVuaToHD6tLBqaRmncJbkTSMJ2DXag6ZyZ4T34nkrUD+tPcN3 6MrTrYNuWGT4vjjyva3n6/uKppBDYop7IMLI8eBscGUWNfBCP2Hg2TUKmw4NtEe7NJvlC8Z3Kiy TlUn9PMABz2dcoZ9rIkTLascGsUVAfkAvH56ImEUAjpmH+4ko+mTYmgSWvC7BSBwi5EFPwa8KxR lVN+hk5LBtHSF8/WkmMu42gF40UvKuSLSXc= X-Google-Smtp-Source: AGHT+IFEqRDUJYWsXaXnRpxZt8GDWr0msOnaosN+/HWENXkbDFim7xaCTynZm5RKBQEYzER6dtAUEw== X-Received: by 2002:a05:6402:278a:b0:5db:f26d:fff8 with SMTP id 4fb4d7f45d1cf-5e0361cbe0amr15216331a12.22.1739958628492; Wed, 19 Feb 2025 01:50:28 -0800 (PST) Received: from localhost.localdomain ([2001:871:5e:517b:7a17:db82:bac2:ea1d]) by smtp.gmail.com with ESMTPSA id 4fb4d7f45d1cf-5dece1b4debsm10158070a12.15.2025.02.19.01.50.27 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Wed, 19 Feb 2025 01:50:28 -0800 (PST) Message-ID: <832effb7f0459161a90b55dc09fec0e98c378bd7.camel@cybertec.at> Subject: Re: PGDG PostgreSQL Debian package: Question on conditions for creation of new cluster From: Laurenz Albe To: Schmid Andreas , "pgsql-general@lists.postgresql.org" Date: Wed, 19 Feb 2025 10:50:27 +0100 In-Reply-To: References: User-Agent: Evolution 3.54.3 (3.54.3-1.fc41) MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On Wed, 2025-02-19 at 08:45 +0000, Schmid Andreas wrote: > 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. I just tried on an Ubuntu system (I think that the packages are pretty much the same), and installing 17.3 created a cluster. I think the Stackoverflow question was about installing 17.3 if v17 is already installed. In that case, no new cluster is created. Yours, Laurenz Albe -- *E-Mail Disclaimer* Der Inhalt dieser E-Mail ist ausschliesslich fuer den bezeichneten Adressaten bestimmt. Wenn Sie nicht der vorgesehene Adressat dieser E-Mail oder dessen Vertreter sein sollten, so beachten Sie bitte, dass jede Form der Kenntnisnahme, Veroeffentlichung, Vervielfaeltigung oder Weitergabe des Inhalts dieser E-Mail unzulaessig ist. Wir bitten Sie, sich in diesem Fall mit dem Absender der E-Mail in Verbindung zu setzen. *CONFIDENTIALITY NOTICE & DISCLAIMER *This message and any attachment are confidential and may be privileged or otherwise protected from disclosure and solely for the use of the person(s) or entity to whom it is intended. If you have received this message in error and are not the intended recipient, please notify the sender immediately and delete this message and any attachment from your system. If you are not the intended recipient, be advised that any use of this message is prohibited and may be unlawful, and you must not copy this message or attachment or disclose the contents to any other person.