| From: | Joe Conway <mail(at)joeconway(dot)com> |
|---|---|
| To: | Christophe Pettus <xof(at)thebuild(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | 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:09:47 |
| Message-ID: | 172a934d-6a5d-4c57-9935-43862025b842@joeconway.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On 9/6/24 22:19, Christophe Pettus wrote:
>> On Sep 6, 2024, at 19:17, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>> What does it matter if someone can see that database XYZ exists,
>> as long as they can't connect to it?
> I think in the OP's case, the database naming convention leaked
> information about customers, but using random DB names (while maybe
> not aesthetically pleasing) gets around that issue.
Yeah, but there are other issues, e.g. leaked usernames of the other
customers too.
There is definitely demand for using PostgreSQL in multitenant use
cases, but there are multiple problems to solve before people with those
use cases will be happy.
I think Tom's suggestion regarding RLS on system catalogs was one
approach bandied about in the past, but unless I am mistaken we never
committed the patch to allow RLS on system catalogs (or did I miss that?)
--
Joe Conway
PostgreSQL Contributors Team
RDS Open Source Databases
Amazon Web Services: https://aws.amazon.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David G. Johnston | 2024-09-07 14:38:35 | Re: [EXT]: Re: BUG #18604: Regression in PostgreSQL 16.4: pg_dump Prevents Essential System Table Modifications |
| Previous Message | Magnus Hagander | 2024-09-07 06:22:31 | Re: BUG #18599: server closed the connection unexpectedly |