Received: from malur.postgresql.org ([217.196.149.56])
	by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256)
	(Exim 4.89)
	(envelope-from <pgsql-hackers-owner+archive@lists.postgresql.org>)
	id 1h8WFA-0003C5-Sh
	for pgsql-hackers@arkaria.postgresql.org; Mon, 25 Mar 2019 20:30:53 +0000
Received: from localhost ([127.0.0.1] helo=malur.postgresql.org)
	by malur.postgresql.org with esmtp (Exim 4.89)
	(envelope-from <pgsql-hackers-owner+archive@lists.postgresql.org>)
	id 1h8WF9-0001Sx-EB
	for pgsql-hackers@arkaria.postgresql.org; Mon, 25 Mar 2019 20:30:51 +0000
Received: from makus.postgresql.org ([2001:4800:3e1:1::229])
	by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256)
	(Exim 4.89)
	(envelope-from <legrand_legrand@hotmail.com>)
	id 1h8WF9-0001Nb-3O
	for pgsql-hackers@lists.postgresql.org; Mon, 25 Mar 2019 20:30:51 +0000
Received: from n3.nabble.com ([162.255.23.22])
	by makus.postgresql.org with esmtp (Exim 4.89)
	(envelope-from <legrand_legrand@hotmail.com>)
	id 1h8WF5-0003Gn-A7
	for pgsql-hackers@postgresql.org; Mon, 25 Mar 2019 20:30:49 +0000
Received: from n3.nabble.com (localhost [127.0.0.1])
	by n3.nabble.com (Postfix) with ESMTP id C378112D2FA26
	for <pgsql-hackers@postgresql.org>; Mon, 25 Mar 2019 13:30:45 -0700 (MST)
Date: Mon, 25 Mar 2019 13:30:45 -0700 (MST)
From: legrand legrand <legrand_legrand@hotmail.com>
To: pgsql-hackers@postgresql.org
Message-ID: <1553545845798-0.post@n3.nabble.com>
In-Reply-To: 
 <CAOBaU_bhG+=5bqMoUEcKF+Yaqk8fqfr5FCwfKS07_tyOUbk9qg@mail.gmail.com>
References: 
 <DB6PR0301MB21352F6210E3B11934B0DCC790B00@DB6PR0301MB2135.eurprd03.prod.outlook.com>
 <6112091549979517@myt5-a323eb993ef7.qloud-c.yandex.net>
 <1550179299067-0.post@n3.nabble.com>
 <2205341550215950@sas1-cd55e40a6ba0.qloud-c.yandex.net>
 <DB6PR0301MB2135B4B1D256F547966A559B90430@DB6PR0301MB2135.eurprd03.prod.outlook.com>
 <CAOBaU_Yq6motvaqXE_vBWf=SsRANij=+jE3Xa4qCmzGb24LkzA@mail.gmail.com>
 <DB6PR0301MB21351B7CDA68EFE4838562EC905C0@DB6PR0301MB2135.eurprd03.prod.outlook.com>
 <CAOBaU_bU1m3_XF5qKYtSj1ua4dxd=FWDyh2SH4rSJAUUfsGmAQ@mail.gmail.com>
 <CAOBaU_bhG+=5bqMoUEcKF+Yaqk8fqfr5FCwfKS07_tyOUbk9qg@mail.gmail.com>
Subject: Re: Planning counters in pg_stat_statements (using pgss_store)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
List-Id: <pgsql-hackers.lists.postgresql.org>
List-Help: <https://lists.postgresql.org/manage/>
List-Subscribe: <https://lists.postgresql.org/manage/>
List-Post: <mailto:pgsql-hackers@lists.postgresql.org>
List-Owner: <mailto:pgsql-hackers-owner@lists.postgresql.org>
List-Archive: <https://www.postgresql.org/list/pgsql-hackers>
Precedence: bulk

As there are now 3 locking times on pgss hash struct, one day or an other, 
somebody will ask for a GUC to disable this feature (to be able to run pgss
unchanged with only one lock as today).

With this GUC, pgss_store should be able to store the query text and
accumulated 
execution duration in the same call (as today).

Will try to provide this soon.




--
Sent from: http://www.postgresql-archive.org/PostgreSQL-hackers-f1928748.html