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 1lUXsE-0003HH-96 for pgsql-hackers@arkaria.postgresql.org; Thu, 08 Apr 2021 16:51:18 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1lUXsD-0006lU-33 for pgsql-hackers@arkaria.postgresql.org; Thu, 08 Apr 2021 16:51:17 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1lUXsC-0006lN-SV for pgsql-hackers@lists.postgresql.org; Thu, 08 Apr 2021 16:51:16 +0000 Received: from new4-smtp.messagingengine.com ([66.111.4.230]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1lUXs7-0006p0-Rt for pgsql-hackers@lists.postgresql.org; Thu, 08 Apr 2021 16:51:15 +0000 Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailnew.nyi.internal (Postfix) with ESMTP id D7908580456; Thu, 8 Apr 2021 12:51:10 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute4.internal (MEProxy); Thu, 08 Apr 2021 12:51:10 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:subject:to :x-me-proxy:x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s= fm2; bh=omzO6Kbk6d0AIio3yoo0j4CA0rg/wW6Y6EG6ziqYv5Y=; b=wTODf4MZ s5FolFUucaM7QMQDmqcfCpiJOh26fc/m1JAGBHayWms71koUBu1KbaIE/Px2xcuH rD9mGw9zDxtoDFFvxuKkAEgwJVXvvv4CSGiBaUSy6pRMdTLqA4ph4vk4hBHjrxbr JphFiFNEVbExy/u19HaBywBwssT9nPg0xMhZDX9E7ZTDp9Fb5NYYJbnT7UAz0DbA bP9XAGPr0hH1RWbodNzenLTY0EC49G3slf5/pp3cdfqDNFcQgu8Lk6tQPUyWkPn2 kl/PPNkEH8TTv3lFk+mrYEqZ2QgrFMDTY0JR3eliXrZ4j0UAIJsiRyAVKltjHvRO ytc8+LuIOQRzUQ== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduledrudejledguddtkecutefuodetggdotefrod ftvfcurfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfgh necuuegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmd enucfjughrpeffhffvuffkgggtugfgjggfsehtkeertddtredunecuhfhrohhmpeetlhhv rghrohcujfgvrhhrvghrrgcuoegrlhhvhhgvrhhrvgesrghlvhhhrdhnohdqihhprdhorh hgqeenucggtffrrghtthgvrhhnpeeufffhjeeiueeuffegvddukeegledtveeivdeiueef ieeivefgteehueefteehvdenucfkphepudeltddrleehrdduledrleehnecuvehluhhsth gvrhfuihiivgeptdenucfrrghrrghmpehmrghilhhfrhhomheprghlvhhhvghrrhgvsegr lhhvhhdrnhhoqdhiphdrohhrgh X-ME-Proxy: Received: from perhan.alvh.no-ip.org (unknown [190.95.19.95]) by mail.messagingengine.com (Postfix) with ESMTPA id 341DC1080054; Thu, 8 Apr 2021 12:51:09 -0400 (EDT) Received: by perhan.alvh.no-ip.org (Postfix, from userid 1000) id DE2AA2A062E; Thu, 8 Apr 2021 12:51:06 -0400 (-04) Date: Thu, 8 Apr 2021 12:51:06 -0400 From: Alvaro Herrera To: Bruce Momjian Cc: Julien Rouhaud , Tom Lane , Nitin Jadhav , Hannu Krosing , Robert Haas , Pavel Stehule , 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? Message-ID: <20210408165106.GA8261@alvherre.pgsql> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <20210408153425.GC2439@momjian.us> User-Agent: Mutt/1.10.1 (2018-07-13) List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On 2021-Apr-08, Bruce Momjian wrote: > pg_stat_activity.queryid is new, but I can imagine cases where you would > join pg_stat_activity to pg_stat_statements to get an estimate of how > long the query will take --- having one using an underscore and another > one not seems odd. OK. So far, you have one vote for queryid (your own) and two votes for query_id (mine and Julien's). And even yourself were hesitating about it earlier in the thread. -- Álvaro Herrera Valdivia, Chile