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 1mnAqm-0006Jp-SW for pgsql-bugs@arkaria.postgresql.org; Wed, 17 Nov 2021 02:39:04 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1mnAql-0007HC-Hh for pgsql-bugs@arkaria.postgresql.org; Wed, 17 Nov 2021 02:39:03 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1mnAql-0007H3-96 for pgsql-bugs@lists.postgresql.org; Wed, 17 Nov 2021 02:39:03 +0000 Received: from out1-smtp.messagingengine.com ([66.111.4.25]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1mnAqi-00065d-TW for pgsql-bugs@lists.postgresql.org; Wed, 17 Nov 2021 02:39:02 +0000 Received: from compute6.internal (compute6.nyi.internal [10.202.2.46]) by mailout.nyi.internal (Postfix) with ESMTP id 08AED5C0197; Tue, 16 Nov 2021 21:39:00 -0500 (EST) Received: from mailfrontend2 ([10.202.2.163]) by compute6.internal (MEProxy); Tue, 16 Nov 2021 21:39:00 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=paquier.xyz; h= date:from:to:cc:subject:message-id:references:mime-version :content-type:in-reply-to; s=fm3; bh=/v1DTFK6XR2nu8cOE3Gl72AM8XJ mk/PBnoFzPd+knrE=; b=TcdcKUD+SWyNIKXn3IgAa6Pn2fMRdA9pVlPMvCVc3F2 AcoDh05y4cR77WZJUlem7sMqy3u75TBu1mx4MZy/ehwOL7O03/zavbZKHNIeUTud zaNf1xHpSuNc/X0DSByJo0g4WuhnyOkbUO2Eh9MWkVWZ29aq+Z/1cG5GL1PAnV24 B86PN3LEWuuWveQpbp0cIYZz+a6GSPtfCPo3V2wfrxiipvscW5wdU7Ad0NEwAAHM Tp66lO4X6n3IN+rEnZK0JTK1OEikaCvU+K/HhJfMaxAWL/4Aou9uoTG6QVhKYbG3 1twBxstf2BLU5mIGGIz/BgcxOwXWsF5I1E4vNoECv6w== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-proxy :x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm1; bh=/v1DTF K6XR2nu8cOE3Gl72AM8XJmk/PBnoFzPd+knrE=; b=IJWvIXDeS51v31Tk8nM047 ml/lMyLycgrwg1mep8Rn7AeRhxrHiXmH4e20taFNeBo64VCZj8bpsLHeScXh5/Z5 vtvb0aDWRXd+KbWjWHwbozsHjPyGIN1O2+KCjsJZgbL8vX1Lz2wfjJnpLR1A362M CtR9APTycmOYojYd2XGEqxS2TkVnRLaZAf1gYGOWgPSrH8MOmTu10VVs1CpGvD74 faoYnb1AVw9PWxgkBW74V7WWXBXdPsIjy1+wJ0klAGIhR7XRxXlc0lJcw8BryWva HrDHwDSoGAItkN/xO0oyuKZK8IF91kuZW0p/WT9B66g5+9vwRNNs7UhJpv86FZsw == X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvuddrfeefgdegkecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenfg hrlhcuvffnffculdejtddmnecujfgurhepfffhvffukfhfgggtuggjsehgtderredttdej necuhfhrohhmpefoihgthhgrvghlucfrrghquhhivghruceomhhitghhrggvlhesphgrqh huihgvrhdrgiihiieqnecuggftrfgrthhtvghrnhepveefgfeugedvjeefjeffkefhfeet keelvdegvdefgeefudejuedtkeehiefgleeunecuvehluhhsthgvrhfuihiivgeptdenuc frrghrrghmpehmrghilhhfrhhomhepmhhitghhrggvlhesphgrqhhuihgvrhdrgiihii X-ME-Proxy: Received: by mail.messagingengine.com (Postfix) with ESMTPA; Tue, 16 Nov 2021 21:38:58 -0500 (EST) Date: Wed, 17 Nov 2021 11:38:55 +0900 From: Michael Paquier To: =?utf-8?Q?Stanis=C5=82aw?= Kodzis Cc: pgsql-bugs@lists.postgresql.org Subject: Re: Postgres14.1 bug with pg_restore and repmgr Message-ID: References: MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="72fVYxUIvmf1d5/B" Content-Disposition: inline In-Reply-To: List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --72fVYxUIvmf1d5/B Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Nov 16, 2021 at 09:34:33AM +0100, Stanis=C5=82aw Kodzis wrote: > There was 14.1 couple days ago and it affected my upgrade from 9.6 to 14. > On 14.0 there was smooth upgrade - now after apt upgrade to 14.1 I have t= he > error(with pg_upgrade cmd on ubuntu 20.4): There has been no changes related to extensions between 14.0 and 14.1 AFAIK, so that looks like an issue with the extension shipped in repmgr and its packaging. > I dunno how to implement this (on 9.6 is already registered) > ALTER EXTENSION "repmgr" > If I register it on 14.1 pg_upgrade won't allow me to continue upgrade. If you want to speed up things, one thing you could do is perhaps drop the extension before the upgrade and re-create it on the new cluster once you are done with pg_upgrade? It is not uncommon to have post-upgrade reconfigurations depending on what you are doing. This one is a bit extreme, and it may not work if that's a packaging issue.. -- Michael --72fVYxUIvmf1d5/B Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAABCgAdFiEEG72nH6vTowiyblFKnvQgOdbyQH0FAmGUaz8ACgkQnvQgOdby QH3TZQ//UsZZl/X0AhTZLiMKeocy3JttGotnUP+o07B99lRwUyQqgV7CGcIJCv4+ IKDb1MZSoKB2Ib5sDvSulfr1QYGNJ24J/WGDvktP14Y1IyOV2jQrCRhCD4kqTxZt jnNNVhI3wlur9MvY+hmOl1kFinLYNVUu+zvFc8JplPNcvTzuAeZUpmSog8TMHaj1 KWm9spIyN4WarWrDB9giw4rZ/IMvRkREwKlxMAcoHxtkPPhG2+n4kNvBCF2WO9GC jBH2M2q/ZLQG0xm8BuekJYYUdzlpixsY4+Fgoh2w4SOL917rTzlxjn2kRZez9rkc h6SQYVnv54sAFaELUmBiUFxBqYv+sNnFArUUI/5lVRRyx/0c/mW2ZTcFyKCZo16y ZN41lvS+Q1n3k4ERwqdCGkWm12LUjw/PHgkJ3MSp7p7YjzZGO4d/TwRDstboFVNF DQdbWcN7i6Uh3i6bK/oSKEAyme68XM4pecghq0WddkfhFqmfOUPY6W1wInOhgkN8 dw75/tcgq3gYrUFXE859ua9tPaPSJdePXsFaDo3dzZosUaam+GqpmeeuIfR7Do9g R5vqSBDoaULyHcYIbRKN9feomTvus+JwDNZhVVFIzFkjXUgS3cijw2TB9xhaBkiw tDusGUJzjUemxCqoTCpk24JxbeuHzMFTwQjkEFOBhMft1r61tr0= =pIXW -----END PGP SIGNATURE----- --72fVYxUIvmf1d5/B--