RE: pg_init_privs corruption.

From: Floris Van Nee <florisvannee(at)Optiver(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Kirill Reshke <reshke(at)double(dot)cloud>
Cc: "pgsql-hackers(at)lists(dot)postgresql(dot)org" <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: RE: pg_init_privs corruption.
Date: 2023-02-17 19:23:45
Message-ID: c5ec75ee718e4b4bac8f8ace49c650ce@opammb0562.comp.optiver.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> Kirill Reshke <reshke(at)double(dot)cloud> writes:
> > As you can see, after drop role there is invalid records in
> > pg_init_privs system relation. After this, pg_dump generate sql
> > statements, some of which are based on content of pg_init_privs, resulting
> in invalid dump.
>

This is as far as I can see the same case as what I reported a few years ago here: https://www.postgresql.org/message-id/flat/1574068566573.13088%40Optiver.com#488bd647ce6f5d2c92764673a7c58289
There was a discussion with some options, but no fix back then.

-Floris

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Andres Freund 2023-02-17 19:41:32 Re: recovery modules
Previous Message Jim Jones 2023-02-17 19:01:35 Re: [PATCH] Add pretty-printed XML output option