MIME-Version: 1.0
In-Reply-To: 
 <CAGA3vBtp2H4+v-AnWLq_w8TVAuHS5++6dHW98YN1-q7N66ywYQ@mail.gmail.com>
References: 
 <CAGA3vBug6Sq_XYLxzmY470WFS6Z3OF28goYzX=QHrCc4hgQSDw@mail.gmail.com>
 <72acf8ae4e56886081b9f632569f290d3246c33b.camel@cybertec.at>
 <CAGA3vBuWjNdz=zfMNvpqYRJRdQCapbexWnD4kgOss2PMbw5ZZw@mail.gmail.com>
 <8536f893e79693bd0a23d4cea7dbe0b6366378df.camel@cybertec.at>
 <CAGA3vBtp2H4+v-AnWLq_w8TVAuHS5++6dHW98YN1-q7N66ywYQ@mail.gmail.com>
From: "David G. Johnston" <david.g.johnston@gmail.com>
Date: Wed, 10 Dec 2025 07:25:29 -0700
Message-ID: 
 <CAKFQuwZducmkxoyh_=gvdHJ2Te5rHGctv70BQQsacmgMMjtZRw@mail.gmail.com>
Subject: Re: database specific pg_read_all_data / pg_write_all_data
To: richard coleman <rcoleman.ascentgl@gmail.com>
Cc: Laurenz Albe <laurenz.albe@cybertec.at>,
	Pgsql-admin <pgsql-admin@lists.postgresql.org>
Content-Type: multipart/alternative; boundary="000000000000e12e95064599ccc2"
Archived-At: 
 <https://www.postgresql.org/message-id/CAKFQuwZducmkxoyh_%3DgvdHJ2Te5rHGctv70BQQsacmgMMjtZRw%40mail.gmail.com>
Precedence: bulk

--000000000000e12e95064599ccc2
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

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=E2=80=99ve claims here do not establish a sol=
id 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.

--000000000000e12e95064599ccc2
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

On Wednesday, December 10, 2025, richard coleman &lt;<a href=3D"mailto:rcol=
eman.ascentgl@gmail.com">rcoleman.ascentgl@gmail.com</a>&gt; wrote:<blockqu=
ote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc s=
olid;padding-left:1ex"><div dir=3D"ltr"><div>I hope that the PostgreSQL dev=
s revisit it in the future with an eye towards making it applicable in more=
 situations.</div></div></blockquote><div><br></div><div>There are setups w=
here roles can access multiple databases and in some of those they have rea=
d/write all privileges and in others they do not?</div><div><br></div><div>=
Fundamentally making group-role memberships per-database is a fundamental c=
hange that seems quite unappealing to attempt without a solid use case that=
 it will enable. =C2=A0iMO you=E2=80=99ve claims here do not establish a so=
lid use case - they are lacking convincing details.=C2=A0 That said, the pr=
oject is open source - you can scratch your own itch.=C2=A0 But the model c=
hange is still a complexity hill to overcome.</div><div><br></div><div>Davi=
d J.</div><div><br></div>

--000000000000e12e95064599ccc2--