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

From Tom Lane
Subject Re: [EXT]: Re: BUG #18604: Regression in PostgreSQL 16.4: pg_dump Prevents Essential System Table Modifications
Date
Msg-id 2410942.1725675471@sss.pgh.pa.us
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
List pgsql-bugs
Christophe Pettus <xof@thebuild.com> writes:
> The real problem you're trying to solve that that users can discover the existence of databases that they can't
connectto.  That's much more imaginable, although I'm not sure how practical it would be.  At minimum, the default
behaviorwould have to be the same as it is now (or lots of things that work now would break), so introducing a new role
privilegeof "can see all databases" wouldn't be a great way forward. 

Even more to the point: that doesn't really seem like a problem
worth putting development and ongoing maintenance effort into.
What does it matter if someone can see that database XYZ exists,
as long as they can't connect to it?

            regards, tom lane



pgsql-bugs by date:

Previous
From: Christophe Pettus
Date:
Subject: Re: [EXT]: Re: BUG #18604: Regression in PostgreSQL 16.4: pg_dump Prevents Essential System Table Modifications
Next
From: Christophe Pettus
Date:
Subject: Re: [EXT]: Re: BUG #18604: Regression in PostgreSQL 16.4: pg_dump Prevents Essential System Table Modifications