Re: BUG #18376: pg_upgrade fails trying to restore privileges on retired function pg_start_backup and pg_stop_backup

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: mrechte(at)gmail(dot)com, pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: BUG #18376: pg_upgrade fails trying to restore privileges on retired function pg_start_backup and pg_stop_backup
Date: 2024-03-04 22:45:55
Message-ID: ZeZPI6roZnW2LeUY@paquier.xyz
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

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

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Noah Misch 2024-03-04 23:05:03 Re: FSM Corruption (was: Could not read block at end of the relation)
Previous Message Ronan Dunklau 2024-03-04 22:21:07 Re: FSM Corruption (was: Could not read block at end of the relation)