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 1kU0Bl-0008T9-8I for pgsql-hackers@arkaria.postgresql.org; Sun, 18 Oct 2020 04:20:57 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1kU0Bh-0004kJ-RU for pgsql-hackers@arkaria.postgresql.org; Sun, 18 Oct 2020 04:20:53 +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 1kU0Bh-0004kC-Kl for pgsql-hackers@lists.postgresql.org; Sun, 18 Oct 2020 04:20:53 +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 1kU0Ba-0003mu-OO for pgsql-hackers@lists.postgresql.org; Sun, 18 Oct 2020 04:20:52 +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 09I4Kbqa157600; Sun, 18 Oct 2020 00:20:37 -0400 From: Tom Lane To: Alvaro Herrera cc: Julien Rouhaud , Bruce Momjian , Robert Haas , Michael Paquier , torikoshia , Atsushi Torikoshi , Tatsuro Yamada , Tomas Vondra , Evgeny Efimkin , PostgreSQL Hackers Subject: Re: Feature improvement: can we add queryId for pg_catalog.pg_stat_activity view? In-reply-to: <20201018030142.GA4069@alvherre.pgsql> References: <20201018030142.GA4069@alvherre.pgsql> Comments: In-reply-to Alvaro Herrera message dated "Sun, 18 Oct 2020 00:01:42 -0300" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <157598.1602994837.1@sss.pgh.pa.us> Date: Sun, 18 Oct 2020 00:20:37 -0400 Message-ID: <157599.1602994837@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk Alvaro Herrera writes: > Wait ... what? I've been thinking that this GUC is just to enable or > disable the computation of query ID, not to change the algorithm to do > so. Do we really need to allow different algorithms in different > sessions? We established that some time ago, no? regards, tom lane