Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1pct3q-0003Pr-BB for pgsql-general@arkaria.postgresql.org; Thu, 16 Mar 2023 19:14:50 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1pct3p-0007Va-3p for pgsql-general@arkaria.postgresql.org; Thu, 16 Mar 2023 19:14:49 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1pct3o-0007VR-P1 for pgsql-general@lists.postgresql.org; Thu, 16 Mar 2023 19:14:48 +0000 Received: from smtp.outgoing.loopia.se ([93.188.3.37]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1pct3m-0003Tz-FH for pgsql-general@postgresql.org; Thu, 16 Mar 2023 19:14:48 +0000 Received: from s807.loopia.se (localhost [127.0.0.1]) by s807.loopia.se (Postfix) with ESMTP id ED0B12F98D26 for ; Thu, 16 Mar 2023 20:14:44 +0100 (CET) Received: from s934.loopia.se (unknown [172.22.191.6]) by s807.loopia.se (Postfix) with ESMTP id DE4E42E2E514; Thu, 16 Mar 2023 20:14:44 +0100 (CET) Received: from s474.loopia.se (unknown [172.22.191.5]) by s934.loopia.se (Postfix) with ESMTP id DAA3E7CEA58; Thu, 16 Mar 2023 20:14:44 +0100 (CET) X-Virus-Scanned: amavisd-new at amavis.loopia.se X-Spam-Flag: NO X-Spam-Score: -1 X-Spam-Level: X-Spam-Status: No, score=-1 tagged_above=-999 required=6.2 tests=[ALL_TRUSTED=-1] autolearn=disabled Received: from s980.loopia.se ([172.22.191.5]) by s474.loopia.se (s474.loopia.se [172.22.190.14]) (amavisd-new, port 10024) with LMTP id uWFdup9Si86S; Thu, 16 Mar 2023 20:14:44 +0100 (CET) X-Loopia-Auth: user X-Loopia-User: daniel@yesql.se X-Loopia-Originating-IP: 89.255.232.193 Received: from smtpclient.apple (customer-89-255-232-193.stosn.net [89.255.232.193]) (Authenticated sender: daniel@yesql.se) by s980.loopia.se (Postfix) with ESMTPSA id 6AF4D22016C5; Thu, 16 Mar 2023 20:14:44 +0100 (CET) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3696.120.41.1.2\)) Subject: Re: pg_upgrade Only the install user can be defined in the new cluster From: Daniel Gustafsson In-Reply-To: Date: Thu, 16 Mar 2023 20:14:43 +0100 Cc: "pgsql-general@postgresql.org" Content-Transfer-Encoding: quoted-printable Message-Id: References: <667112E0-5A1C-4F74-86F8-54B121C2336C@yesql.se> <021ED6C2-C01F-4E5B-8415-10C1BE29FCBA@yesql.se> To: =?utf-8?Q?D=C3=A1vid_Suchan?= X-Mailer: Apple Mail (2.3696.120.41.1.2) List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk > On 16 Mar 2023, at 15:56, D=C3=A1vid Suchan = wrote: >=20 > So I tried upgrading into this brand new cluster I created(using = initdb -D /somedatapathichose). Running the upgrade with --check worked, = it returned message that the clusters are identical. Then I stopped the = new cluster, and ran the pg_upgrade without --check, which resulted in = another: > Checking database user is the install user pg_upgrade --check does not alter the new cluster in any way, so you = must have some form of processing on your system that configured the new cluster = with roles (and possibly other things) in between these runs. -- Daniel Gustafsson