From: Michael Paquier <michael@paquier.xyz>
To: mrechte@gmail.com
To: 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
Date: Tue, 5 Mar 2024 07:45:55 +0900
Message-ID: <ZeZPI6roZnW2LeUY@paquier.xyz> (raw)
In-Reply-To: <18376-d420b8068805622e@postgresql.org>
References: <18376-d420b8068805622e@postgresql.org>
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:
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
Attachments:
signature.asc (application/pgp-signature, 832B) download
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-bugs@postgresql.org
Cc: michael@paquier.xyz, 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
In-Reply-To: <ZeZPI6roZnW2LeUY@paquier.xyz>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox