From: Tom Lane <tgl@sss.pgh.pa.us>
To: loren@paradigm.xyz
cc: pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #17626: Permission denied errors should list role as well as
 user
In-reply-to: <17626-644f053cc20e1ba3@postgresql.org>
References: <17626-644f053cc20e1ba3@postgresql.org>
Comments: In-reply-to PG Bug reporting form <noreply@postgresql.org>
	message dated "Sat, 01 Oct 2022 21:09:54 -0000"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <1425127.1664805055.1@sss.pgh.pa.us>
Date: Mon, 03 Oct 2022 09:50:55 -0400
Message-ID: <1425128.1664805055@sss.pgh.pa.us>
Archived-At: 
 <https://www.postgresql.org/message-id/1425128.1664805055%40sss.pgh.pa.us>
Precedence: bulk

PG Bug reporting form <noreply@postgresql.org> writes:
> I'm running this set of commands:
> create user elevated_user IN ROLE pg_read_all_data;
> create user regular_user;
> create table foo (id int);
> set role elevated_user;
> select * from foo; -- works
> set role regular_user;
> select * from foo; -- errors

> The error message looks like "user=elevated_user ERROR:  permission denied
> for table foo".

No ... it just looks like

regression=> select * from foo; -- errors
ERROR:  permission denied for table foo

I don't know where "user=elevated_user" is coming from in your
environment, but it seems like it must be from client-side code
that's not tracking the active role correctly.

			regards, tom lane