Re: [EXT]: Re: BUG #18604: Regression in PostgreSQL 16.4: pg_dump Prevents Essential System Table Modifications

Поиск
Список
Период
Сортировка
От Christophe Pettus
Тема Re: [EXT]: Re: BUG #18604: Regression in PostgreSQL 16.4: pg_dump Prevents Essential System Table Modifications
Дата
Msg-id 831E0C7F-4E37-45F9-AA05-04648077FD8D@thebuild.com
обсуждение исходный текст
Ответ на Re: [EXT]: Re: BUG #18604: Regression in PostgreSQL 16.4: pg_dump Prevents Essential System Table Modifications  (Tom Lane <tgl@sss.pgh.pa.us>)
Ответы RE: [EXT]: Re: BUG #18604: Regression in PostgreSQL 16.4: pg_dump Prevents Essential System Table Modifications
Список pgsql-bugs

> On Sep 7, 2024, at 10:16, Tom Lane <tgl@sss.pgh.pa.us> wrote:
>
> Still, making such a change would amount to actively supporting RLS
> on catalogs, rather than just a laissez-faire "you can use it if it
> works" approach.

I don't want to get into analysis paralysis on this, but I think it makes more sense to have proactive multi-tenancy
features,rather than trying to press the existing infrastructure into service for it.  This means it's a couple of
majorversions out at a minimum, which is annoying for existing users who want multi-tenancy based on databases.  But
companieslike Heroku have been making it (somewhat imperfectly) work for over a decade now, so it's not impossible. 


В списке pgsql-bugs по дате отправления: