Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1u1mkF-0083MS-M1 for pgsql-sql@arkaria.postgresql.org; Mon, 07 Apr 2025 13:42:35 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1u1mkD-00GeO4-VK for pgsql-sql@arkaria.postgresql.org; Mon, 07 Apr 2025 13:42:34 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1u1mkD-00GeNw-MP for pgsql-sql@lists.postgresql.org; Mon, 07 Apr 2025 13:42:34 +0000 Received: from mail-oa1-x2f.google.com ([2001:4860:4864:20::2f]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.96) (envelope-from ) id 1u1mkB-003vWq-24 for pgsql-sql@lists.postgresql.org; Mon, 07 Apr 2025 13:42:33 +0000 Received: by mail-oa1-x2f.google.com with SMTP id 586e51a60fabf-2c1c9b7bd9aso2656468fac.0 for ; Mon, 07 Apr 2025 06:42:31 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1744033349; x=1744638149; darn=lists.postgresql.org; h=cc:to:subject:message-id:date:from:mime-version:from:to:cc:subject :date:message-id:reply-to; bh=SXJq1fbG1V08qctYWlluNdKD7lwAyoZqL3z9QUmQlZY=; b=E99v5Z0hxRKhsZxEwV7AvvDMbHjXmHsBWyYsdiyAv4IsuDg9hWAjgTlwbMs4+40LyZ 8JNfCW44E4pZywPznNatkJz0MKnzhPETp66TpDF8itgogyUTjVTkahMaKfnAf3YhMUn7 ujjgwmi0bJa4AaCcK8iXCep+TCaSB42+rdoJnNm4sQU3TVs7dohc+gpkkFXDsYEhhVb5 4Szxnd5SmdtcS8lh4fwYK1ctlL2knTobxMurz+CRmBiMGgbQFati2rGNhDcgaihRrRPw mKuzj44ii/oV8zt/ZJLpiGG83rSlxJSp/GtUQ/JznVyuSYT4L/tedaOs7ZF77QSVq+1i J/4g== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1744033349; x=1744638149; h=cc:to:subject:message-id:date:from:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=SXJq1fbG1V08qctYWlluNdKD7lwAyoZqL3z9QUmQlZY=; b=CoHRe56UGaNCImmME+Fh1jCp/Ji+nRaCxgmUedTRK36sRtWfZYMLgXJYb3Qi2EQx12 xfKFk3sd1WixaNVB4NnyyGh+XfFyhlvV4BnLj6paRpGHcnF14IaMW42in6gX1xfFwuKl WIVQGrgGWSVSUD9LgZj5RXK0EcyrBwImgrtnCrU6EsCLLI3OMmvkEe2ddcgWy5VnGAMx SyXcINu+P+sf1eyC3Ty8HSM2Yt4ZgNdGBHp2o96rSRoZQ5o+sQ6l79v+LyGBSvS//R8V sscouomqACH/8GMtfpLB84YfE3XE3yvMgk2xa9YpFFy8fo+udt/dv97jO5xSCDdOI3kr AFyQ== X-Gm-Message-State: AOJu0Yx4rdU1e5WsHd3oBqshSzixCX5b92Qeph1W6DKQZxns4w+xc41U 2fv32FS+fLfcy/k50JpZgdXbHhS/V38DfThBayv9sinhhuA8LoHlh/ppqUr8YFKLRnL96HNxeMc bIkpbLVftnOJjhDbUIu6Sb1Pz/+1WZQ== X-Gm-Gg: ASbGncu9ACiiwAePas8w3ixSBPPQerLDrfkSwvIkUTmiRBB+VWC+PbxPNOJf/1mOJBh 4+CvcUaftd4gtLqyjhKRugYlITKXDb/M26VGejgT4fnaeXO8KNItOgfgCZ2WJHPObXDfYpm6oBh LOjuo8bOkDIf/DJ35tXmKvk8d8 X-Google-Smtp-Source: AGHT+IHsVAow3q1qbgEXSXBxKAS12IGV7tT3MGBD1JRGjMWEQBqbLJIWg/pSClruePDH9NjJF+dEg134Uh9Y4Ie+ukU= X-Received: by 2002:a05:6871:418e:b0:2c1:461f:309a with SMTP id 586e51a60fabf-2cca18c7d0fmr6932910fac.8.1744033349344; Mon, 07 Apr 2025 06:42:29 -0700 (PDT) MIME-Version: 1.0 Received: by 2002:a8a:c4e:0:b0:589:13f9:e937 with HTTP; Mon, 7 Apr 2025 06:42:28 -0700 (PDT) From: "David G. Johnston" Date: Mon, 7 Apr 2025 06:42:28 -0700 X-Gm-Features: ATxdqUE_wEGuH81uTMu5I_DdfDWiII5QOHv6sJaWeTk1ANZvn3zFBB-fZyyTcNk Message-ID: Subject: Re: Re: Revoke Connect Privilege from Database not working To: "Ing. Marijo Kristo" Cc: "pgsql-sql@lists.postgresql.org" Content-Type: multipart/alternative; boundary="00000000000043a563063230685f" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --00000000000043a563063230685f Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Monday, April 7, 2025, Ing. Marijo Kristo 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=3D# \du vault_admin; > List of roles > Role name | Attributes > -------------+------------------------ > vault_admin | Superuser, Create role > > postgres=3D# set role vault_admin; > You are setting role to another role that has superuser which is basically pointless. Use =E2=80=9Cgranted by=E2=80=9D in your revoke command. If that works thi= s isn=E2=80=99t a bug. David J. --00000000000043a563063230685f Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Monday, April 7, 2025, Ing. Marijo Kristo <marijo.kristo@icloud.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.

<= /div>

post= gres=3D# \du vault_admin;
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 List of roles
=C2=A0 Role n= ame=C2=A0 |=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 Attributes
<= div>-------------+------------------------
vault_admin |= Superuser, Create role

postgres=3D# set role = vault_admin;

You are = setting role to another role that has superuser which is basically pointles= s.

Use =E2=80=9Cgranted by=E2=80=9D in your revoke= command.=C2=A0 If that works this isn=E2=80=99t a bug.

David J.

--00000000000043a563063230685f--