| From: | Christophe Pettus <xof(at)thebuild(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Basha <Basha(at)maxcontact(dot)com>, Joe Conway <mail(at)joeconway(dot)com>, PostgreSQL Bug List <pgsql-bugs(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: [EXT]: Re: BUG #18604: Regression in PostgreSQL 16.4: pg_dump Prevents Essential System Table Modifications |
| Date: | 2024-09-07 17:29:14 |
| Message-ID: | 831E0C7F-4E37-45F9-AA05-04648077FD8D@thebuild.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
> On Sep 7, 2024, at 10:16, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)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 major versions out at a minimum, which is annoying for existing users who want multi-tenancy based on databases. But companies like Heroku have been making it (somewhat imperfectly) work for over a decade now, so it's not impossible.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2024-09-07 18:21:33 | Re: [EXT]: Re: BUG #18604: Regression in PostgreSQL 16.4: pg_dump Prevents Essential System Table Modifications |
| Previous Message | Tom Lane | 2024-09-07 17:16:51 | Re: [EXT]: Re: BUG #18604: Regression in PostgreSQL 16.4: pg_dump Prevents Essential System Table Modifications |