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

From Floris Van Nee
Subject Re: incorrect pg_dump output due to not handling dropped rolescorrectly
Date
Msg-id 1574024173786.96623@Optiver.com
Whole thread Raw
In response to Re: incorrect pg_dump output due to not handling dropped roles correctly  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: incorrect pg_dump output due to not handling dropped rolescorrectly  (Michael Paquier <michael@paquier.xyz>)
List pgsql-bugs
> Yeah, I think that would work.  Obviously best to test in a throwaway
> database ...

Thanks, Tom. Fixed it with that query.

As for the proper fix, indeed it looks like the 'drop role' needs to be taught to update pg_init_privs.

-Floris




pgsql-bugs by date:

Previous
From: Tomas Vondra
Date:
Subject: Re: 回复: 回复: 回复: BUG #16101: tables in the DB is not available after pg_restore
Next
From: PG Bug reporting form
Date:
Subject: BUG #16121: 12 regression: Volatile function in target list subquery behave as stable