| From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
|---|---|
| To: | Joe Conway <mail(at)joeconway(dot)com> |
| Cc: | Christophe Pettus <xof(at)thebuild(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Basha <Basha(at)maxcontact(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 14:38:35 |
| Message-ID: | CAKFQuwb+=niX=uqoX2EuOX_uSfiCuOv+cAXs1wW8vE0GC-wanw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Saturday, September 7, 2024, Joe Conway <mail(at)joeconway(dot)com> wrote:
>
>
> Yeah, but there are other issues, e.g. leaked usernames of the other
> customers too.
Yeah…multi-tenant clusters are great so long as you aren’t giving out
logins to tenants. For tenants that need a login to the database they
really need their own cluster and OS-level resource management.
I wonder how hard a “cluster coordinator” binary would be to implement -
something that takes an overall configuration and some shared memory and
effectively allocates those among multiple clusters on the same host. You
can get some of this, like a total connection count, from a pooler.
That said, I’d need to go back and see the arguments for why we don’t just
filter the list of globals to whatever the logged in role is capable of
using. I wonder whether the concerns are with schema objects and globals
are just collateral damage.
David J.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2024-09-07 15:28:54 | Re: [EXT]: Re: BUG #18604: Regression in PostgreSQL 16.4: pg_dump Prevents Essential System Table Modifications |
| Previous Message | Joe Conway | 2024-09-07 14:09:47 | Re: [EXT]: Re: BUG #18604: Regression in PostgreSQL 16.4: pg_dump Prevents Essential System Table Modifications |