Re: pg_init_privs corruption. - Mailing list pgsql-hackers

From Tom Lane
Subject Re: pg_init_privs corruption.
Date
Msg-id 2769218.1676666279@sss.pgh.pa.us
Whole thread Raw
In response to RE: pg_init_privs corruption.  (Floris Van Nee <florisvannee@Optiver.com>)
Responses Re: pg_init_privs corruption.
Re: pg_init_privs corruption.
Re: pg_init_privs corruption.
List pgsql-hackers
Floris Van Nee <florisvannee@Optiver.com> writes:
> 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.

Hmm, so Stephen was opining that the extension's objects shouldn't
have gotten these privs attached in the first place.  I'm not
quite convinced about that one way or the other, but if you buy it
then maybe this situation is unreachable once we fix that.  I'm
not sure though.  It's still clear that we are making ACL entries
that aren't reflected in pg_shdepend, and that seems bad.

            regards, tom lane



pgsql-hackers by date:

Previous
From: Jeff Davis
Date:
Subject: Re: Move defaults toward ICU in 16?
Next
From: Jeff Davis
Date:
Subject: Re: Move defaults toward ICU in 16?