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 ) id 1mbNbA-0004aM-02 for pgsql-bugs@arkaria.postgresql.org; Fri, 15 Oct 2021 13:50:12 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1mbNb7-0008H6-M0 for pgsql-bugs@arkaria.postgresql.org; Fri, 15 Oct 2021 13:50:09 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1mbNb7-0008Gw-Ed for pgsql-bugs@lists.postgresql.org; Fri, 15 Oct 2021 13:50:09 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1mbNb5-0007Rz-GJ for pgsql-bugs@lists.postgresql.org; Fri, 15 Oct 2021 13:50:09 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.15.2/8.15.2) with ESMTP id 19FDo5KW952988; Fri, 15 Oct 2021 09:50:05 -0400 From: Tom Lane To: "Andrey V. Lepikhov" cc: PostgreSQL mailing lists Subject: Re: SET SESSION AUTHORIZATION command doesn't update status of backend In-reply-to: <76ae5aaf-1843-4d84-0430-f35da7f786b9@postgrespro.ru> References: <76ae5aaf-1843-4d84-0430-f35da7f786b9@postgrespro.ru> Comments: In-reply-to "Andrey V. Lepikhov" message dated "Fri, 15 Oct 2021 11:19:20 +0500" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <952986.1634305805.1@sss.pgh.pa.us> Date: Fri, 15 Oct 2021 09:50:05 -0400 Message-ID: <952987.1634305805@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk "Andrey V. Lepikhov" 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