Re: database specific pg_read_all_data / pg_write_all_data - Mailing list pgsql-admin

From David G. Johnston
Subject Re: database specific pg_read_all_data / pg_write_all_data
Date
Msg-id CAKFQuwZducmkxoyh_=gvdHJ2Te5rHGctv70BQQsacmgMMjtZRw@mail.gmail.com
Whole thread Raw
In response to Re: database specific pg_read_all_data / pg_write_all_data  (richard coleman <rcoleman.ascentgl@gmail.com>)
Responses Re: database specific pg_read_all_data / pg_write_all_data
Re: database specific pg_read_all_data / pg_write_all_data
List pgsql-admin
On Wednesday, December 10, 2025, richard coleman <rcoleman.ascentgl@gmail.com> wrote:
I hope that the PostgreSQL devs revisit it in the future with an eye towards making it applicable in more situations.

There are setups where roles can access multiple databases and in some of those they have read/write all privileges and in others they do not?

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.  iMO you’ve claims here do not establish a solid use case - they are lacking convincing details.  That said, the project is open source - you can scratch your own itch.  But the model change is still a complexity hill to overcome.

David J.

pgsql-admin by date:

Previous
From: richard coleman
Date:
Subject: Re: database specific pg_read_all_data / pg_write_all_data
Next
From: Laurenz Albe
Date:
Subject: Re: database specific pg_read_all_data / pg_write_all_data