From: Tom Lane <tgl@sss.pgh.pa.us>
To: Erik Wienhold <ewie@ewie.name>
cc: Stuart McGraw <smcgraw@mtneva.com>, pgsql-general@lists.postgresql.org
Subject: Re: Restoring default privileges on objects
In-reply-to: <1166048641.281962.1693308151542@office.mailbox.org>
References: <96d6885a-5e25-9ae8-4a1a-d7e557a5fe9c@mtneva.com> <1166048641.281962.1693308151542@office.mailbox.org>
Comments: In-reply-to Erik Wienhold <ewie@ewie.name>
	message dated "Tue, 29 Aug 2023 13:22:31 +0200"
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-ID: <1006396.1693318485.1@sss.pgh.pa.us>
Content-Transfer-Encoding: quoted-printable
Date: Tue, 29 Aug 2023 10:14:45 -0400
Message-ID: <1006397.1693318485@sss.pgh.pa.us>
Archived-At: <https://www.postgresql.org/message-id/1006397.1693318485%40sss.pgh.pa.us>
Precedence: bulk

Erik Wienhold <ewie@ewie.name> writes:
> On 29/08/2023 03:23 CEST Stuart McGraw <smcgraw@mtneva.com> wrote:
>> If I've done a GRANT or REVOKE on some of the tables, how do I restore
>> the default privileges so that the =E2=80=9CAccess privileges=E2=80=9D =
appears empty
>> again?  I re-granted what I think are the default privileges but the
>> "Access privileges" column for that table contains "user1=3DarwdDxt/use=
r1"
>> rather than being blank.  This is Postgresql-14.

> Yes, "user1=3DarwdDxt/user1" matches the default privileges if user1 is =
the table
> owner.

Right.  There is no (supported) way to cause the ACL entry to go back
to null.  It starts life that way as an ancient hack to save a step
during object creation.  But the moment you do anything to the object's
privileges, the NULL is replaced by an explicit representation of the
default privileges, which is then modified per whatever command you
are giving.  After that the privileges will always be explicit.

There's been occasional discussion of changing this behavior, but
it'd take work and it'd likely add about as much surprise as it
removes.  People have been used to this quirk for a long time.

			regards, tom lane