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 1tkmfq-006m0w-Vt for pgsql-general@arkaria.postgresql.org; Wed, 19 Feb 2025 16:11:47 +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 1tkmfp-00Adbo-I3 for pgsql-general@arkaria.postgresql.org; Wed, 19 Feb 2025 16:11:45 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1tkmfo-00Adam-MV for pgsql-general@lists.postgresql.org; Wed, 19 Feb 2025 16:11:45 +0000 Received: from fout-b7-smtp.messagingengine.com ([202.12.124.150]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1tkmfl-001n6D-2T for pgsql-general@lists.postgresql.org; Wed, 19 Feb 2025 16:11:44 +0000 Received: from phl-compute-06.internal (phl-compute-06.phl.internal [10.202.2.46]) by mailfout.stl.internal (Postfix) with ESMTP id 305B81140169; Wed, 19 Feb 2025 11:11:40 -0500 (EST) Received: from phl-mailfrontend-02 ([10.202.2.163]) by phl-compute-06.internal (MEProxy); Wed, 19 Feb 2025 11:11:40 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=aklaver.com; h= cc:content-transfer-encoding:content-type:content-type:date:date :from:from:in-reply-to:in-reply-to:message-id:mime-version :references:reply-to:subject:subject:to:to; s=fm2; t=1739981500; x=1740067900; bh=Zs+6HYWmPYcnClDhMPRWsAqaY0gvvOc5Ku9Yy3uB+Ik=; b= eervqNf2WUa3/B7ciLY8dzpGWPr/1hQNxK/o+5GnBrzbF/o2ZACOatvhUzosxCb2 qZusPcuP7gkFKvLK9aP9MlYlFMFt/u8CuRZGtW7ZMEJXB1Sx0sx4FPJe8W7uMgqY s3oowZtP86KATI0YFzaSI2u7w5X3pxuQMgWFetl7Ev3UKXULpTD3nWZY9mr6zEoH kX3Jg1IpV6afVruyMYMbDSddhvJWGNKxyR49eSFgOoV/LKtwSv8aaJF/GcgjKTGA RE+kA1VdlXUX9mFR7oHvToId2WcgoqH0rL3Wk9wxeWRooKXvsr01FqIsVg2Kozpx 2uDv74xGcuFviQwK+bQN2w== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :content-type:date:date:feedback-id:feedback-id:from:from :in-reply-to:in-reply-to:message-id:mime-version:references :reply-to:subject:subject:to:to:x-me-proxy:x-me-sender :x-me-sender:x-sasl-enc; s=fm3; t=1739981500; x=1740067900; bh=Z s+6HYWmPYcnClDhMPRWsAqaY0gvvOc5Ku9Yy3uB+Ik=; b=AuNjQ2cFkgKHT6tGa uBcBZlbI0yacNm/9NBxvHa9k1zUi63FuXngqxXqCEUZagOqyou9kmrBPTn9OMeci l+QMk5Xrsfdb3QXRi98w/cdjPNI4xC7ex5St3/KW/zGREm/h0v4zreQDFci2NDzJ qsIAje6qQTzi40+bIcj3PqquT+qU4ffAVypwpcNEDd3lrs6nNhvo0egkRXl+wxGT HzcISUpJkPB2GuUd2wmAn69QZBr/JGLuP7IoY9vnH4YedYdswdWoFAWPj0YRGX16 loDJ/60uOfouBhDDb/RrM6btKQec934iD05tWZCiCYzgocNxCXRfaJVMkU8upflE 1YZqA== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeefvddrtddtgdeigeejtdcutefuodetggdotefrod ftvfcurfhrohhfihhlvgemucfhrghsthforghilhdpggftfghnshhusghstghrihgsvgdp uffrtefokffrpgfnqfghnecuuegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivg hnthhsucdlqddutddtmdenucfjughrpefkffggfgfuvfhfhfgjtgfgsehtkeertddtvdej necuhfhrohhmpeetughrihgrnhcumfhlrghvvghruceorggurhhirghnrdhklhgrvhgvrh esrghklhgrvhgvrhdrtghomheqnecuggftrfgrthhtvghrnhepffelgeeifefgveduhedt hfekuedtffejveegffegjeevtdehgfduieetfeehjeehnecuvehluhhsthgvrhfuihiivg eptdenucfrrghrrghmpehmrghilhhfrhhomheprggurhhirghnrdhklhgrvhgvrhesrghk lhgrvhgvrhdrtghomhdpnhgspghrtghpthhtohepvddpmhhouggvpehsmhhtphhouhhtpd hrtghpthhtoheprghnughrvggrshdrshgthhhmihgusegsugdrshhordgthhdprhgtphht thhopehpghhsqhhlqdhgvghnvghrrghlsehlihhsthhsrdhpohhsthhgrhgvshhqlhdroh hrgh X-ME-Proxy: Feedback-ID: i76984098:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Wed, 19 Feb 2025 11:11:38 -0500 (EST) Message-ID: <2998a590-e131-4756-91e2-7b071d02652b@aklaver.com> Date: Wed, 19 Feb 2025 08:11:37 -0800 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: AW: PGDG PostgreSQL Debian package: Question on conditions for creation of new cluster To: Schmid Andreas , "pgsql-general@lists.postgresql.org" References: <832effb7f0459161a90b55dc09fec0e98c378bd7.camel@cybertec.at> <30722d87e4c642d0bc6bf4048d250c28@bd.so.ch> Content-Language: en-US From: Adrian Klaver In-Reply-To: <30722d87e4c642d0bc6bf4048d250c28@bd.so.ch> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On 2/19/25 05:22, Schmid Andreas wrote: >> -----Ursprüngliche Nachricht----- > > Well, according to the last comment below the Stack Overflow question, it was about installing 17.3 with a v14 cluster already present. > Anyways, I now tried on an Ubuntu 24.04 machine as well, and installing 17.3 alone created a cluster. > Cleaned up the machine, then installed 15.11, which created a cluster. Installed 16.7 alongside, which did not create an additional cluster. So it's probably not a 17.3 problem. > Same outcome on Ubuntu 20.04. Which was explained to you in the comments to the SO question. There is no 'Installed 16.7 alongside ...'. As was explained this is just minor version upgrade to Postgres 16 and will only upgrade the binaries and associated libraries for the major version 16. > > Maybe there generally is no cluster created if there is one present already. I now checked /usr/share/postgresql-common/maintscripts-functions which is installed by the postgresql-common_273.pgdg24.04+1_all.deb package. This script contains the create_main_cluster() function, which according to a comment "skips if any other cluster already exists". > So could it be that this function has been updated recently? Can you point me to the repo where this script is maintained? Do man pg_createcluster. -- Adrian Klaver adrian.klaver@aklaver.com