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 1li3I6-0008IU-Bc for pgsql-hackers@arkaria.postgresql.org; Sat, 15 May 2021 23:01:50 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1li3I3-0005h5-Jm for pgsql-hackers@arkaria.postgresql.org; Sat, 15 May 2021 23:01:47 +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 1li3I2-0005gb-Ig for pgsql-hackers@lists.postgresql.org; Sat, 15 May 2021 23:01:47 +0000 Received: from [66.111.4.221] (helo=new1-smtp.messagingengine.com) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1li3Hz-0002kk-6c for pgsql-hackers@lists.postgresql.org; Sat, 15 May 2021 23:01:45 +0000 Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailnew.nyi.internal (Postfix) with ESMTP id 88084580B49; Sat, 15 May 2021 19:01:31 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute1.internal (MEProxy); Sat, 15 May 2021 19:01:31 -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=KFlDzMK4u8w7noNZX1PrYcjfQJu0qjUekZBMOMro4sQ=; b=N5G4pvOO 4wuB4PcC5jajtyybBVeJZ/5+4C9grXBt84x/PYyZgjM5gie7E6hadslfGfsfXiVf uLqC6K1EZuAbJu9Zmonx/nabJHXcuciKYBVNBoz/f632JPvL7I3HQM2nSef4yWYk 6m1b/3eE8iwgcvAbF6qKZk5uw0xEYL6wOvmeMUmqxVDE9/UK7G3XR+o6bMnorNP9 BT1nIvPxa/abA7N2fGxwyTW2YZs9z/nZB2Q6nPWpv57nB0OMN4mj0zJ9NJ8aNzbH TRZgs4qmgsfHD7cU+R0x6MbcVx1XWMXxddDr1IZ8T+8KoaCjoha3OhGWQnQaJDWM mZiFUspLTVADKA== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduledrvdeiuddgudejucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhepfffhvffukfggtggugfgjfgesthekredttderudenucfhrhhomheptehlvhgr rhhoucfjvghrrhgvrhgruceorghlvhhhvghrrhgvsegrlhhvhhdrnhhoqdhiphdrohhrgh eqnecuggftrfgrthhtvghrnhepueffhfejieeuueffgedvudekgeeltdeviedvieeufeei ieevgfetheeufeethedvnecukfhppeduledtrdelhedrudelrdelheenucevlhhushhtvg hrufhiiigvpedtnecurfgrrhgrmhepmhgrihhlfhhrohhmpegrlhhvhhgvrhhrvgesrghl vhhhrdhnohdqihhprdhorhhg X-ME-Proxy: Received: from perhan.alvh.no-ip.org (unknown [190.95.19.95]) by mail.messagingengine.com (Postfix) with ESMTPA; Sat, 15 May 2021 19:01:29 -0400 (EDT) Received: by perhan.alvh.no-ip.org (Postfix, from userid 1000) id 8EDCA2A0BB7; Sat, 15 May 2021 19:01:25 -0400 (-04) Date: Sat, 15 May 2021 19:01:25 -0400 From: Alvaro Herrera To: Bruce Momjian Cc: Julien Rouhaud , Fujii Masao , Pavel Stehule , Kyotaro Horiguchi , Magnus Hagander , Michael Paquier , Andres Freund , Tom Lane , Stephen Frost , Christoph Berg , Peter Eisentraut , PostgreSQL Hackers Subject: Re: compute_query_id and pg_stat_statements Message-ID: <20210515230125.GA2951@alvherre.pgsql> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <20210515213258.GA21748@momjian.us> User-Agent: Mutt/1.10.1 (2018-07-13) X-Host-Lookup-Failed: Reverse DNS lookup failed for 66.111.4.221 (deferred) List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On 2021-May-15, Bruce Momjian wrote: > On Sat, May 15, 2021 at 02:21:59PM -0400, Álvaro Herrera wrote: > > I wonder why the initial line says "query hash" instead of "query > > identifier". Do we want to say "hash" everywhere? Why didn't we name > > the GUC "compute_query_hash" in that case? > > It is queryid (no underscore) in pg_stat_statements, which was a whole > different discussion. ;-) Yeah, I realize that, but I wonder if we shouldn't use the term "query identifier" instead of "query hash" in that paragraph. > I also added Alvaro as an author of the compute_query_id item. I've been wondering if I should ask to stick my name in other features I helped get committed -- specifically the PQtrace() item and autovacuum for partitioned tables. I'll go comment in the release notes thread. -- Álvaro Herrera Valdivia, Chile "Digital and video cameras have this adjustment and film cameras don't for the same reason dogs and cats lick themselves: because they can." (Ken Rockwell)