Re: Re: Revoke Connect Privilege from Database not working

From: "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>
To: "Ing(dot) Marijo Kristo" <marijo(dot)kristo(at)icloud(dot)com>
Cc: "pgsql-sql(at)lists(dot)postgresql(dot)org" <pgsql-sql(at)lists(dot)postgresql(dot)org>
Subject: Re: Re: Revoke Connect Privilege from Database not working
Date: 2025-04-07 13:42:28
Message-ID: CAKFQuwa7m2smqqpgPetw=i8Aj-xqg9Zjc5Z2aX3AUwNh96WnXw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs pgsql-sql

On Monday, April 7, 2025, Ing. Marijo Kristo <marijo(dot)kristo(at)icloud(dot)com>
wrote:
>
>
> Seems like a bug to me.
> Can someone else verifiy this ?
>

It would help greatly if you create a reproducer that starts from a clean
install, creates the roles and database, and demonstrates the issue.

> postgres=# \du vault_admin;
> List of roles
> Role name | Attributes
> -------------+------------------------
> vault_admin | Superuser, Create role
>
> postgres=# set role vault_admin;
>

You are setting role to another role that has superuser which is basically
pointless.

Use “granted by” in your revoke command. If that works this isn’t a bug.

David J.

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Tom Lane 2025-04-07 13:48:14 Re: BUG #18880: Can't have a database without having postgres as a db_name and username
Previous Message Zhijie Hou (Fujitsu) 2025-04-07 09:58:39 RE: BUG #18815: Logical replication worker Segmentation fault

Browse pgsql-sql by date

  From Date Subject
Next Message Ing. Marijo Kristo 2025-04-07 14:27:41 Aw:  Re: Re: Revoke Connect Privilege from Database not working
Previous Message Ing. Marijo Kristo 2025-04-07 08:53:07 Aw:  Re: Revoke Connect Privilege from Database not working