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 1rhH4a-00AZBm-7Q for pgsql-bugs@arkaria.postgresql.org; Mon, 04 Mar 2024 22:46:16 +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 1rhH4X-00BQTf-U4 for pgsql-bugs@arkaria.postgresql.org; Mon, 04 Mar 2024 22:46:14 +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 1rhH4X-00BQTW-Lp for pgsql-bugs@lists.postgresql.org; Mon, 04 Mar 2024 22:46:14 +0000 Received: from wfout8-smtp.messagingengine.com ([64.147.123.151]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1rhH4T-002ry1-PF for pgsql-bugs@lists.postgresql.org; Mon, 04 Mar 2024 22:46:12 +0000 Received: from compute3.internal (compute3.nyi.internal [10.202.2.43]) by mailfout.west.internal (Postfix) with ESMTP id DEC581C000BA; Mon, 4 Mar 2024 17:46:08 -0500 (EST) Received: from mailfrontend2 ([10.202.2.163]) by compute3.internal (MEProxy); Mon, 04 Mar 2024 17:46:09 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=paquier.xyz; h= cc: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=fm1; t=1709592368; x=1709678768; bh=qLEHn0OYEZ OVzDAF6+jyi7wWIS6GpLfynC07rKc42YA=; b=Q0C9SIp/LyoWkSgbyL0cIh0RAb 02tRCRWjTO9vPaQeFc4KT0gNXQLtKwmeEWV6kNbm+olAcHhZ5pa6KiGe0feaJ7GL Mol71s2ljiKv9DVjCrWDRXPTmq5uWtPLZa+zJXri80sizQDAlsXbYqp8MTUZNgS3 OE8xMgUT9KxGQ5FrizKSbDaXTCjVWZ1Ty9XEgyM1C0XloqnEMCI/5cWtZvNZgv04 witiaUT+K1tYrDHmrowKg+V6CpbdPOpIaElvZ5nuD0ZEvTjzY24MGyUqiNfqTK95 B/lGbtmOgy+aDnUnP7cQENK/JaALCCg3b98/QzO6i7eIjGgfvRRLPlKwa6Wg== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc: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-proxy:x-me-sender:x-me-sender:x-sasl-enc; s= fm1; t=1709592368; x=1709678768; bh=qLEHn0OYEZOVzDAF6+jyi7wWIS6G pLfynC07rKc42YA=; b=Q0DkeL8ZItsI5A9P8l+xcQ71K4/pqcQsj9z7Ej7Nkukv iUqXt5zIJdCFFpcDz0hWSlu6cpUO2/4TjkHSO7BeM2awyOPNpXBMIGGRFpzB6JGK yRZnZS9JM+8L74IoonQMiAt+3et2uKeY7xVmQ13F4DUD3mcO/UUC9ZiW+pDhFab4 QNluHqrj61/41UKdKKt9YuhP56COhGl9dZgni1qHHF8Mu4vLcoPoRL7+U/RGvLki NoTL2lQhEDqEoSwtrJNzlkfTTPukKFI8LSPsSJ+AimXvWfLbebLdjT6Ilps3RRos jO7oxumVchHBozHVqL/Tq0nOWmU5+Iq8vcr7kjbi9g== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvledrheekgddtudcutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecufghrlhcuvffnffculdefhedmnecujfgurhepfffhvf fukfhfgggtuggjsehgtderredttddvnecuhfhrohhmpefoihgthhgrvghlucfrrghquhhi vghruceomhhitghhrggvlhesphgrqhhuihgvrhdrgiihiieqnecuggftrfgrthhtvghrnh epffdufeeflefghfekudekkeevvddugfeiteekkeduleefvefhhffftdduffeiuedtnecu ffhomhgrihhnpehpohhsthhgrhgvshhqlhdrohhrghenucevlhhushhtvghrufhiiigvpe dtnecurfgrrhgrmhepmhgrihhlfhhrohhmpehmihgthhgrvghlsehprghquhhivghrrdig hiii X-ME-Proxy: Feedback-ID: i0fe9450f:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Mon, 4 Mar 2024 17:46:07 -0500 (EST) Date: Tue, 5 Mar 2024 07:45:55 +0900 From: Michael Paquier To: mrechte@gmail.com, pgsql-bugs@lists.postgresql.org Subject: Re: BUG #18376: pg_upgrade fails trying to restore privileges on retired function pg_start_backup and pg_stop_backup Message-ID: References: <18376-d420b8068805622e@postgresql.org> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="u69lxUPxhDKGtHTB" Content-Disposition: inline In-Reply-To: <18376-d420b8068805622e@postgresql.org> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --u69lxUPxhDKGtHTB Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Mar 04, 2024 at 09:56:35AM +0000, PG Bug reporting form wrote: > Those functions being dropped in PG15, one should not try to restore > privileges on them. This is a known issue, and it is much larger than just ACLs on functions, because we need to take care of much more object types. Another area is catalog attribute renames, for example. See this thread:=20 https://www.postgresql.org/message-id/f85991ad-bbd4-ad57-fde4-e12f0661dbf0%= 40postgrespro.ru A patch has been proposed there, but I don't think we were much happy about the fact to plug in this knowledge directly to pg_upgrade, because at some extent this also impacts logical dumps taken from older versions, and even logical replication setups. -- Michael --u69lxUPxhDKGtHTB Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAABCgAdFiEEG72nH6vTowiyblFKnvQgOdbyQH0FAmXmTyMACgkQnvQgOdby QH2dtA//R7oBnkQn+TapW8bzJsoAZlnEjwiHWMX5xphjw9hUJSL6/93UK4pKtiZV OobNmO777hI3jYWG1aGERp/5zbG3PuwIV8U4ENUMajUxDEbKsaG4DNWKnY2P11SM kVdDFr0KQA1e0ofLLRZgDo9RGl56fmeFxwN3et5iGXT/fMYxdSsOXfaT6lExNwj6 nosq9hlZruli8QPKK2uZWj3mTkD99VXWOOtpovrD4imZka51YeUKTij+GvaL+sSR p0lLGYjlhzBApvNL/2fXSBDS3S9IQ7CsU19AqPzT7qP2tgs8VOybO0tB/YqV090C sIeCALqtDE+eRVVIWW9agw3EOoVK92ZTagVc2PsdIedDiBdmStKRaMMAX+8pfjK5 VnE6B75T5AeDtRY1Et5MMbWcA1PmSmSbNl138nmJu/n1pVYWAXigrrJPKqIj3uvS uLCEtZOmG+sJpwbAX17M11rz+a0Arbcfo+a38cmlZJAO68tF6NP+20SeGeqnkvzJ Lpv2vdOMX/abYnNoG87Ww/9BGGqP5U7JjmkKpDzzMlwbI0rV49NpCbO+d4rN4tnt degsV5KuVG+Rml4CkM95RJhX13ZJJZTRXSALkr6ZfndDxDDAkmAFlZFh30rE5XBP OZWe9dUoSee5kEW92UtfS9XjOUYfjNXPSBeB7LM1hRx1iOZhxmQ= =o5R9 -----END PGP SIGNATURE----- --u69lxUPxhDKGtHTB--