Re: pg_init_privs corruption.

Поиск
Список
Период
Сортировка
Искать
От
Tom Lane
Тема
Re: pg_init_privs corruption.
Дата
Msg-id
2769218.1676666279@sss.pgh.pa.us
Ответ на
Список
Дерево обсуждения
pg_init_privs corruption. Kirill Reshke <reshke@double.cloud>
Re: pg_init_privs corruption. Tom Lane <tgl@sss.pgh.pa.us>
RE: pg_init_privs corruption. Floris Van Nee <florisvannee@Optiver.com>
Re: pg_init_privs corruption. Tom Lane <tgl@sss.pgh.pa.us>
Re: pg_init_privs corruption. Robert Haas <robertmhaas@gmail.com>
Re: pg_init_privs corruption. Greg Stark <stark@mit.edu>
Re: pg_init_privs corruption. Stephen Frost <sfrost@snowman.net>
Floris Van Nee  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 по дате отправления
От: Jeff Davis
Дата:
От: Jeff Davis
Дата:
FAQ