pg.ddx.io pgsql-bugs@postgresql.org mailing list archive
help / color / mirror / Atom feedpg_upgrade fails if privileges have been granted on pg_start_backup()/pg_stop_backup() in the old cluster
2+ messages / 2 participants
[nested] [flat]
* pg_upgrade fails if privileges have been granted on pg_start_backup()/pg_stop_backup() in the old cluster
@ 2022-11-02 14:47 Helena Zetterström <helena.zetterstrom@chalmers.se>
0 siblings, 1 reply; 2+ messages in thread
From: Helena Zetterström @ 2022-11-02 14:47 UTC (permalink / raw)
To: pgsql-bugs@lists.postgresql.org <pgsql-bugs@lists.postgresql.org>
Hi,
In version 15 the functions pg_start_backup()/pg_stop_backup() have been renamed to pg_backup_start()/pg_backup_stop().
If privileges on these functions have been granted in the old cluster the pg_upgrade fails.
Our barman user has been granted execute priviliges on these function in PostgreSQL 14 and to avoid the pg_upgrade to fail we had to revoke these privileges in the old cluster before running the pg_upgrade.
No warning/notification is given about this when running pg_upgrade --check.
I don´t know if this is a bug or not but it is really inconvenient to have the pg_upgrade fail/crash (child process exited abnormally: status 256) due to it being unable to grant execute on these no longer existing functions.
It would have been good if a notification about this could have been shown when running the pg_upgrade with the --check option before performing the actual upgrade.
Best regards,
Helena Zetterström
^ permalink raw reply [nested|flat] 2+ messages in thread
* Re: pg_upgrade fails if privileges have been granted on pg_start_backup()/pg_stop_backup() in the old cluster
@ 2022-11-03 02:30 Noah Misch <noah@leadboat.com>
parent: Helena Zetterström <helena.zetterstrom@chalmers.se>
0 siblings, 0 replies; 2+ messages in thread
From: Noah Misch @ 2022-11-03 02:30 UTC (permalink / raw)
To: Helena Zetterström <helena.zetterstrom@chalmers.se>; +Cc: pgsql-bugs@lists.postgresql.org <pgsql-bugs@lists.postgresql.org>
On Wed, Nov 02, 2022 at 02:47:27PM +0000, Helena Zetterström wrote:
> In version 15 the functions pg_start_backup()/pg_stop_backup() have been renamed to pg_backup_start()/pg_backup_stop().
>
> If privileges on these functions have been granted in the old cluster the pg_upgrade fails.
> Our barman user has been granted execute priviliges on these function in PostgreSQL 14 and to avoid the pg_upgrade to fail we had to revoke these privileges in the old cluster before running the pg_upgrade.
> No warning/notification is given about this when running pg_upgrade --check.
> I don´t know if this is a bug or not but it is really inconvenient to have the pg_upgrade fail/crash (child process exited abnormally: status 256) due to it being unable to grant execute on these no longer existing functions.
> It would have been good if a notification about this could have been shown when running the pg_upgrade with the --check option before performing the actual upgrade.
This thread was an unsuccessful attempt to fix that class of problem:
https://www.postgresql.org/message-id/flat/f85991ad-bbd4-ad57-fde4-e12f0661dbf0%40postgrespro.ru
^ permalink raw reply [nested|flat] 2+ messages in thread
end of thread, other threads:[~2022-11-03 02:30 UTC | newest]
Thread overview: 2+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2022-11-02 14:47 pg_upgrade fails if privileges have been granted on pg_start_backup()/pg_stop_backup() in the old cluster Helena Zetterström <helena.zetterstrom@chalmers.se>
2022-11-03 02:30 ` Noah Misch <noah@leadboat.com>
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