Re: incorrect pg_dump output due to not handling dropped roles correctly - Mailing list pgsql-bugs

From Tom Lane
Subject Re: incorrect pg_dump output due to not handling dropped roles correctly
Date
Msg-id 29913.1573835973@sss.pgh.pa.us
Whole thread Raw
In response to incorrect pg_dump output due to not handling dropped roles correctly  (Floris Van Nee <florisvannee@Optiver.com>)
Responses Re: incorrect pg_dump output due to not handling dropped rolescorrectly  (Floris Van Nee <florisvannee@Optiver.com>)
List pgsql-bugs
Floris Van Nee <florisvannee@Optiver.com> writes:
> I noticed I wasn't able to apply my usual pg_dump schema output without errors anymore after I dropped some roles.
Aftersome digging, I found it has to do with Postgres not correctly updating the pg_init_privs table upon dropping
roles.I can reproduce a similar scenario with the following steps (output from v13devel, but AFAIK all versions
affected,I ran into the issue on v11.2): 

Hm, looks like we forgot to teach the dependency mechanism about
pg_init_privs privileges?  (I didn't look yet.)

> Can I manually fix this by updating pg_init_privs catalog table?

Yeah, I think that would work.  Obviously best to test in a throwaway
database ...

            regards, tom lane



pgsql-bugs by date:

Previous
From: Marco Cuccato
Date:
Subject: LDAPS trusted ca support
Next
From: PG Bug reporting form
Date:
Subject: BUG #16118: subsequent to Postgres server 12.1 patch, database won't start