Received: from malur.postgresql.org ([217.196.149.56])
	by arkaria.postgresql.org with esmtps
 (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256)
	(Exim 4.92)
	(envelope-from <pgsql-admin-owner+archive@lists.postgresql.org>)
	id 1prjty-0006r3-2U
	for pgsql-admin@arkaria.postgresql.org; Wed, 26 Apr 2023 18:30:02 +0000
Received: from localhost ([127.0.0.1] helo=malur.postgresql.org)
	by malur.postgresql.org with esmtp (Exim 4.92)
	(envelope-from <pgsql-admin-owner+archive@lists.postgresql.org>)
	id 1prjtx-0006nK-1i
	for pgsql-admin@arkaria.postgresql.org; Wed, 26 Apr 2023 18:30:01 +0000
Received: from makus.postgresql.org ([2001:4800:3e1:1::229])
	by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256)
	(Exim 4.92)
	(envelope-from <ewie@ewie.name>)
	id 1prjtw-0006nB-NG
	for pgsql-admin@lists.postgresql.org; Wed, 26 Apr 2023 18:30:00 +0000
Received: from mout-u-107.mailbox.org ([2001:67c:2050:101:465::107])
	by makus.postgresql.org with esmtps  (TLS1.3) tls
 TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
	(Exim 4.94.2)
	(envelope-from <ewie@ewie.name>)
	id 1prjtu-0022ac-Bv
	for pgsql-admin@lists.postgresql.org; Wed, 26 Apr 2023 18:29:59 +0000
Received: from smtp202.mailbox.org (smtp202.mailbox.org [10.196.197.202])
	(using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)
	 key-exchange ECDHE (P-384) server-signature RSA-PSS (4096 bits)
 server-digest SHA256)
	(No client certificate requested)
	by mout-u-107.mailbox.org (Postfix) with ESMTPS id 4Q66q40WVQz9sR0;
	Wed, 26 Apr 2023 20:29:52 +0200 (CEST)
Date: Wed, 26 Apr 2023 20:29:51 +0200 (CEST)
From: Erik Wienhold <ewie@ewie.name>
To: Holger Jakobs <holger@jakobs.com>, pgsql-admin@lists.postgresql.org,
	richard coleman <rcoleman.ascentgl@gmail.com>
Message-ID: <874394544.1204470.1682533791565@office.mailbox.org>
In-Reply-To: <fd81361e-fa84-1d75-d944-1c590de0e424@jakobs.com>
References: 
 <CAGA3vBvanu7UBtaaVv9PH25Ko==5F2wewhPWTTra8wqexdDAdQ@mail.gmail.com>
 <2058602074.1048315.1682529431551@office.mailbox.org>
 <CAGA3vBtQKHuX2XLOq31-k+iywhsHwWTUTjBiAyZJmtXZutQB+Q@mail.gmail.com>
 <fd81361e-fa84-1d75-d944-1c590de0e424@jakobs.com>
Subject: Re: how to list privileges on the database object itself via SQL?
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
X-Priority: 3
Importance: Normal
List-Id: <pgsql-admin.lists.postgresql.org>
List-Help: <https://lists.postgresql.org/manage/>
List-Subscribe: <https://lists.postgresql.org/manage/>
List-Post: <mailto:pgsql-admin@lists.postgresql.org>
List-Owner: <mailto:pgsql-admin-owner@lists.postgresql.org>
List-Archive: <https://www.postgresql.org/list/pgsql-admin>
Archived-At: 
 <https://www.postgresql.org/message-id/874394544.1204470.1682533791565%40office.mailbox.org>
Precedence: bulk

> On 26/04/2023 19:55 CEST Holger Jakobs <holger@jakobs.com> wrote:
>
> Am 26.04.23 um 19:53 schrieb richard coleman:
>
> > ERROR: role "role" does not exist
> >  LINE 3: WHERE grantee = 'role'::regrole AND privilege_type I...
> >  ^
> >  SQL state: 42704
> >  Character: 151
>
> If you want to use the SQL statements used by psql on older versions of
> PostgreSQL, you should use the old version of psql.

'role'::regrole  works perfectly fine since pg9.5 if the role exists.
Use  grantee::regrole::text = 'role'  to be safe.

--
Erik