Re: database specific pg_read_all_data / pg_write_all_data

On 12/10/25 12:33, Tom Lane wrote:
> "David G. Johnston" <david.g.johnston@gmail.com> writes:
>> Fundamentally making group-role memberships per-database is a fundamental
>> change that seems quite unappealing to attempt without a solid use case
>> that it will enable.
> 
> Yeah, I think this would be bad from both the intellectual-complexity
> and implementation-difficulty standpoints.
> 
> However ... we've had multiple requests in the past to invent
> database-specific roles.  I wonder if it'd suffice for Richard's
> purposes to create such roles and grant them pg_read_all_data.


There is a significant real world demand for doing multi-tenant 
PostgreSQL by having one tenant per database. It is not ideal by any 
means, but a substantial number of folks use that strategy whether we 
like it or not.

Anything we can do to make it less sketchy and painful would be useful 
indeed.

-- 
Joe Conway
PostgreSQL Contributors Team
Amazon Web Services: https://aws.amazon.com