Re: database specific pg_read_all_data / pg_write_all_data

On Wed, 2025-12-10 at 09:10 -0500, richard coleman wrote:
> Running many clusters on a single server, while possible, reduces the amount of memory
> available to each cluster and each database process users run respectively.

Yes, but not a by much.

> ALTER DEFAULT PRIVLIGES doesn't work on schema that doesn't exist at that time that command was run.

That is not true.  The IN SCHEMA clause is optional.
You have to run one ALTER DEFAULT PRIVILEGES for each role that is to create tables, but
if you have many such roles, you are probably doing something wrong.

> I am sorry to hear that you think "pg_read_all_data" is ugly.

That is a purely personal judgement.  I am sure many people find the feature useful.

> That built-in role and others like it have proven very useful for a fairly common
> use case; a small group of users that must share database objects between them without
> having to constantly rejigger privileges on those objects.

I cannot claim to know what people do out there, but I must say that I haven't
encountered many such setups in the field.  Usually such "ad hoc" schemes run into
trouble by the time when people want to drop tables.

Yours,
Laurenz Albe