| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Floris Van Nee <florisvannee(at)Optiver(dot)com> |
| 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-15 16:39:33 |
| Message-ID: | 29913.1573835973@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
Floris Van Nee <florisvannee(at)Optiver(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | PG Bug reporting form | 2019-11-15 19:14:33 | BUG #16118: subsequent to Postgres server 12.1 patch, database won't start |
| Previous Message | Marco Cuccato | 2019-11-15 15:53:30 | LDAPS trusted ca support |