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 1li1uM-0005VW-GK for pgsql-hackers@arkaria.postgresql.org; Sat, 15 May 2021 21:33:14 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1li1uL-0005OI-66 for pgsql-hackers@arkaria.postgresql.org; Sat, 15 May 2021 21:33:13 +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 1li1uK-0005O9-UT for pgsql-hackers@lists.postgresql.org; Sat, 15 May 2021 21:33:12 +0000 Received: from momjian.us ([72.94.173.45]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1li1uH-00014R-8g for pgsql-hackers@lists.postgresql.org; Sat, 15 May 2021 21:33:11 +0000 Received: from bruce by momjian.us with local (Exim 4.92) (envelope-from ) id 1li1u6-0002l9-3D; Sat, 15 May 2021 17:32:58 -0400 Date: Sat, 15 May 2021 17:32:58 -0400 From: Bruce Momjian To: Alvaro Herrera 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: <20210515213258.GA21748@momjian.us> References: <20210515182159.GA11009@alvherre.pgsql> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <20210515182159.GA11009@alvherre.pgsql> 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 Sat, May 15, 2021 at 02:21:59PM -0400, Álvaro Herrera wrote: > I commented out the release notes para that is now wrong. What remains > is this: > > Move query hash computation from pg_stat_statements to the core server (Julien Rouhaud) > > We could perhaps add something like > > Extension pg_stat_statements continues to work without requiring any > configuration changes. > > but that seems a bit pointless. Or maybe > > Extension pg_stat_statements automatically enables query identifier > computation if compute_query_id is set to auto. Third-party modules > to compute query identifiers can be installed and used if this is set > to off. > OK, new text is: Move query hash computation from pg_stat_statements to the core server (Julien Rouhaud) The new server variable compute_query_id's default of 'auto' will automatically enable query id computation when this extension is loaded. I also added Alvaro as an author of the compute_query_id item. > 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. ;-) > Anyway, let me remind you that it is pretty common to require initdb > during the beta period. True. -- Bruce Momjian https://momjian.us EDB https://enterprisedb.com If only the physical world exists, free will is an illusion.