Re: [EXT]: Re: BUG #18604: Regression in PostgreSQL 16.4: pg_dump Prevents Essential System Table Modifications - Mailing list pgsql-bugs

From Joe Conway
Subject Re: [EXT]: Re: BUG #18604: Regression in PostgreSQL 16.4: pg_dump Prevents Essential System Table Modifications
Date
Msg-id 172a934d-6a5d-4c57-9935-43862025b842@joeconway.com
Whole thread Raw
In response to Re: [EXT]: Re: BUG #18604: Regression in PostgreSQL 16.4: pg_dump Prevents Essential System Table Modifications  (Christophe Pettus <xof@thebuild.com>)
Responses Re: [EXT]: Re: BUG #18604: Regression in PostgreSQL 16.4: pg_dump Prevents Essential System Table Modifications
Re: [EXT]: Re: BUG #18604: Regression in PostgreSQL 16.4: pg_dump Prevents Essential System Table Modifications
List pgsql-bugs
On 9/6/24 22:19, Christophe Pettus wrote:
>> On Sep 6, 2024, at 19:17, Tom Lane <tgl@sss.pgh.pa.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



pgsql-bugs by date:

Previous
From: Magnus Hagander
Date:
Subject: Re: BUG #18599: server closed the connection unexpectedly
Next
From: "David G. Johnston"
Date:
Subject: Re: [EXT]: Re: BUG #18604: Regression in PostgreSQL 16.4: pg_dump Prevents Essential System Table Modifications