From: Andrey Lepikhov <a.lepikhov@postgrespro.ru>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: PostgreSQL mailing lists <pgsql-bugs@lists.postgresql.org>
Subject: Re: SET SESSION AUTHORIZATION command doesn't update status of backend
Date: Fri, 15 Oct 2021 22:44:41 +0500
Message-ID: <9ed84986-76dd-774c-14b5-3e41e79d376f@postgrespro.ru> (raw)
In-Reply-To: <952987.1634305805@sss.pgh.pa.us>
References: <76ae5aaf-1843-4d84-0430-f35da7f786b9@postgrespro.ru>
<952987.1634305805@sss.pgh.pa.us>
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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-bugs@postgresql.org
Cc: a.lepikhov@postgrespro.ru, tgl@sss.pgh.pa.us, pgsql-bugs@lists.postgresql.org
Subject: Re: SET SESSION AUTHORIZATION command doesn't update status of backend
In-Reply-To: <9ed84986-76dd-774c-14b5-3e41e79d376f@postgrespro.ru>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox