From: Tom Lane <tgl@sss.pgh.pa.us>
To: Floris Van Nee <florisvannee@Optiver.com>
Cc: pgsql-bugs@lists.postgresql.org <pgsql-bugs@lists.postgresql.org>
Cc: Ferdi Smit <FerdiSmit@Optiver.com>
Cc: Stephen Frost <sfrost@snowman.net>
Subject: Re: incorrect pg_dump output due to not handling dropped roles correctly
Date: Fri, 15 Nov 2019 11:39:33 -0500
Message-ID: <29913.1573835973@sss.pgh.pa.us> (raw)
In-Reply-To: <1573808483712.96817@Optiver.com>
References: <1573808483712.96817@Optiver.com>
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. After some 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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-bugs@postgresql.org
Cc: tgl@sss.pgh.pa.us, florisvannee@Optiver.com, FerdiSmit@Optiver.com, sfrost@snowman.net
Subject: Re: incorrect pg_dump output due to not handling dropped roles correctly
In-Reply-To: <29913.1573835973@sss.pgh.pa.us>
References: <1573808483712.96817@Optiver.com> <29913.1573835973@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox