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

Поиск
Список
Период
Сортировка
От Michael Paquier
Тема Re: BUG #18376: pg_upgrade fails trying to restore privileges on retired function pg_start_backup and pg_stop_backup
Дата
Msg-id ZeZPI6roZnW2LeUY@paquier.xyz
обсуждение исходный текст
Ответ на BUG #18376: pg_upgrade fails trying to restore privileges on retired function pg_start_backup and pg_stop_backup  (PG Bug reporting form <noreply@postgresql.org>)
Список 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

Вложения

В списке pgsql-bugs по дате отправления:

Предыдущее
От: Ronan Dunklau
Дата:
Сообщение: Re: FSM Corruption (was: Could not read block at end of the relation)
Следующее
От: Noah Misch
Дата:
Сообщение: Re: FSM Corruption (was: Could not read block at end of the relation)