Horton

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

Christophe Pettus <xof@thebuild.com>

View thread
From: Christophe Pettus <xof@thebuild.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Basha <Basha@maxcontact.com>, Joe Conway <mail@joeconway.com>, PostgreSQL Bug List <pgsql-bugs@lists.postgresql.org>
Date: 2024-09-07T17:29:14Z
Lists: 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 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.