From: Tom Lane <tgl@sss.pgh.pa.us>
To: "Ing. Marijo Kristo" <marijo.kristo@icloud.com>
cc: pgsql-sql@lists.postgresql.org
Subject: Re: Revoke Connect Privilege from Database not working
In-reply-to: <6C13A1CC-3841-4A5E-BC78-C8F9C5B120BB@icloud.com>
References: <18873-c148b32c0e501cc0@postgresql.org>
 <6C13A1CC-3841-4A5E-BC78-C8F9C5B120BB@icloud.com>
Comments: In-reply-to "Ing. Marijo Kristo" <marijo.kristo@icloud.com>
	message dated "Mon, 31 Mar 2025 17:26:13 +0200"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <346226.1743516829.1@sss.pgh.pa.us>
Date: Tue, 01 Apr 2025 10:13:49 -0400
Message-ID: <346227.1743516829@sss.pgh.pa.us>
Archived-At: 
 <https://www.postgresql.org/message-id/346227.1743516829%40sss.pgh.pa.us>
Precedence: bulk

"Ing. Marijo Kristo" <marijo.kristo@icloud.com> writes:
>> Removing the connect privilege with the Postgres Superuser and with the
>> Vault Admin user does not work.
>> postgres=# revoke connect on database "disp_db" from
>> "dev_oidc-m-kristo-rewe-group-at-2025_02_28T09_06_30+00:00";
>> REVOKE

REVOKE is not being as helpful as it could be here, perhaps:
it is failing to tell you that it's a no-op because there
is no such privilege.  You never granted connect on disp_db
to that user so you can't revoke it either.

The privilege that exists by default, per [1], is that
database connect privileges are granted to PUBLIC (the
pseudo-group of all users).  If that's not what you want,
you have to do

revoke connect on database "disp_db" from public;

and then grant it out again to the users who should have it.

			regards, tom lane

[1] https://www.postgresql.org/docs/current/ddl-priv.html