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

From: PG Bug reporting form <noreply(at)postgresql(dot)org>
To: pgsql-bugs(at)lists(dot)postgresql(dot)org
Cc: mrechte(at)gmail(dot)com
Subject: BUG #18376: pg_upgrade fails trying to restore privileges on retired function pg_start_backup and pg_stop_backup
Date: 2024-03-04 09:56:35
Message-ID: 18376-d420b8068805622e@postgresql.org
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

The following bug has been logged on the website:

Bug reference: 18376
Logged by: Marc Rechté
Email address: mrechte(at)gmail(dot)com
PostgreSQL version: 16.2
Operating system: RHEL 8 (clone)
Description:

We got a pg_upgrade failure when upgrading from a PG14 to a PG16 instance:

pg_restore: de l'entrée TOC 3279 ; 0 0 ACL FUNCTION
"pg_start_backup"("label" "text", "fast" boolean, "exclusive" boolean)
postgres
pg_restore: erreur : could not execute query: ERROR: function
pg_catalog.pg_start_backup(text, boolean, boolean) does not exist
La commande était : GRANT ALL ON FUNCTION
"pg_catalog"."pg_start_backup"("label" "text", "fast" boolean, "exclusive"
boolean) TO "barman";

Those functions being dropped in PG15, one should not try to restore
privileges on them.

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Hayato Kuroda (Fujitsu) 2024-03-04 12:52:22 RE: BUG #18369: logical decoding core on AssertTXNLsnOrder()
Previous Message Rintaro.Ikeda 2024-03-04 08:35:25 RE:Undetected deadlock between client backend and startup processes on a standby (Previously, Undetected deadlock between primary and standby processes)