Major Version Upgrade failure due to orphan roles entries in catalog - Mailing list pgsql-bugs

From Virender Singla
Subject Major Version Upgrade failure due to orphan roles entries in catalog
Date
Msg-id CAM6Zo8woa62ZFHtMKox6a4jb8qQ=w87R2L0K8347iE-juQL2EA@mail.gmail.com
Whole thread Raw
Responses Re: Major Version Upgrade failure due to orphan roles entries in catalog
Re: Major Version Upgrade failure due to orphan roles entries in catalog
List pgsql-bugs
Hi,

We have identified an issue causing upgrade failures. The following steps detail how to reproduce the issue:

Create an orphan role entry

/* Postgres version:: PostgreSQL 16.6 */ 
/* The same can be reproduced in version 17 as well */

create role my_group;
create role dropped_member;
begin;
grant my_group to dropped_member;
OTHER SESSION: drop role dropped_member;
BACK IN ORIGINAL SESSION:
commit;

Upgrade to Postgres v17

And the upgrade fails with an error :

GRANT "my_group" TO "" WITH INHERIT TRUE GRANTED BY "postgres";
ERROR: zero-length delimited identifier at or near """"

The issue seems to be coming from pg_dumpall for building grants during pg_upgrade.


-Virender

pgsql-bugs by date:

Previous
From: Robert Sjöblom
Date:
Subject: Re: BUG #18802: password field in log
Next
From: PG Bug reporting form
Date:
Subject: BUG #18803: ERROR: wrong varnullingrels (b) (expected (b 4)) for Var 2/1