Re: incorrect pg_dump output due to not handling dropped roles correctly

From: Floris Van Nee <florisvannee(at)Optiver(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: "pgsql-bugs(at)lists(dot)postgresql(dot)org" <pgsql-bugs(at)lists(dot)postgresql(dot)org>, "Ferdi Smit" <FerdiSmit(at)Optiver(dot)com>, Stephen Frost <sfrost(at)snowman(dot)net>
Subject: Re: incorrect pg_dump output due to not handling dropped roles correctly
Date: 2019-11-17 20:56:13
Message-ID: 1574024173786.96623@Optiver.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message PG Bug reporting form 2019-11-18 01:26:30 BUG #16121: 12 regression: Volatile function in target list subquery behave as stable
Previous Message Tomas Vondra 2019-11-17 19:35:05 Re: 回复： 回复： 回复： BUG #16101: tables in the DB is not available after pg_restore