Re: SET SESSION AUTHORIZATION command doesn't update status of backend - Mailing list pgsql-bugs

From Tom Lane
Subject Re: SET SESSION AUTHORIZATION command doesn't update status of backend
Date
Msg-id 952987.1634305805@sss.pgh.pa.us
Whole thread Raw
In response to SET SESSION AUTHORIZATION command doesn't update status of backend  ("Andrey V. Lepikhov" <a.lepikhov@postgrespro.ru>)
Responses Re: SET SESSION AUTHORIZATION command doesn't update status of backend  (Andrey Lepikhov <a.lepikhov@postgrespro.ru>)
List pgsql-bugs
"Andrey V. Lepikhov" <a.lepikhov@postgrespro.ru> writes:
> Nikita Degtyarev (n.degtyarev@postgrespro.ru) reported a suspicious 
> behaviour of a SET SESSION AUTHORIZATION command. If you switch user in 
> a session:
> [ pg_stat_activity doesn't change ]

I don't think this is a bug.  pg_stat_activity is reporting the session's
login identity, and that seems fine, though maybe the documentation about
it needs to be clarified.

            regards, tom lane



pgsql-bugs by date:

Previous
From: "Andrey V. Lepikhov"
Date:
Subject: SET SESSION AUTHORIZATION command doesn't update status of backend
Next
From: PG Bug reporting form
Date:
Subject: BUG #17231: ERROR: tuple concurrently updated