Re: SET SESSION AUTHORIZATION command doesn't update status of backend

From: Andrey Lepikhov <a(dot)lepikhov(at)postgrespro(dot)ru>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: PostgreSQL mailing lists <pgsql-bugs(at)lists(dot)postgresql(dot)org>
Subject: Re: SET SESSION AUTHORIZATION command doesn't update status of backend
Date: 2021-10-15 17:44:41
Message-ID: 9ed84986-76dd-774c-14b5-3e41e79d376f@postgrespro.ru
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On 15/10/21 18:50, Tom Lane wrote:
> 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.
Thank you. Documentation is quite correct. I should be more attentive.

--
regards,
Andrey Lepikhov
Postgres Professional

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Tom Lane 2021-10-15 18:24:51 Re: BUG #17231: ERROR: tuple concurrently updated
Previous Message PG Bug reporting form 2021-10-15 17:38:36 BUG #17231: ERROR: tuple concurrently updated