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 1io7YX-0000m1-U2
	for pgsql-hackers@arkaria.postgresql.org; Sun, 05 Jan 2020 15:11:06 +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 1io7YV-0001BJ-Ta
	for pgsql-hackers@arkaria.postgresql.org; Sun, 05 Jan 2020 15:11:03 +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 1io7YV-0001BB-Gt
	for pgsql-hackers@lists.postgresql.org; Sun, 05 Jan 2020 15:11:03 +0000
Received: from n3.nabble.com ([162.255.23.22])
	by makus.postgresql.org with esmtp (Exim 4.92)
	(envelope-from <legrand_legrand@hotmail.com>)
	id 1io7YO-0004Ex-Nm
	for pgsql-hackers@postgresql.org; Sun, 05 Jan 2020 15:11:02 +0000
Received: from n3.nabble.com (localhost [127.0.0.1])
	by n3.nabble.com (Postfix) with ESMTP id E616319F20DB9
	for <pgsql-hackers@postgresql.org>; Sun,  5 Jan 2020 08:10:55 -0700 (MST)
Date: Sun, 5 Jan 2020 08:10:55 -0700 (MST)
From: legrand legrand <legrand_legrand@hotmail.com>
To: pgsql-hackers@postgresql.org
Message-ID: <1578237055901-0.post@n3.nabble.com>
In-Reply-To: 
 <CAOBaU_bKDoMxEWLqJue8ZS-kamcwKS2zUROONjEtp_sHmbBegg@mail.gmail.com>
References: 
 <CAOBaU_Y6drTjKBC8HeyTEyW1RffFwgiT3Mr3Yfm=YBf0e68tWw@mail.gmail.com>
 <CAOBaU_Y12bn0tOdN9RMBZn29bfYYH11b2CwKO1RO7dX9fQ3aZA@mail.gmail.com>
 <OSBPR01MB46163FDEF109B96C60A7989294770@OSBPR01MB4616.jpnprd01.prod.outlook.com>
 <CAOBaU_bzrbAO2amK55AQF3=ivgX6YjOBzZ4bBiHKf_faLK5-Gg@mail.gmail.com>
 <OSBPR01MB46160534A6DF796D180FA88E94700@OSBPR01MB4616.jpnprd01.prod.outlook.com>
 <CAOBaU_YKtC78KmEc_W98yz=BGKd3Lgx-q7D37_sTA9VdsW+xOQ@mail.gmail.com>
 <OSBPR01MB461651369C5B06C4BAEDF4D3944F0@OSBPR01MB4616.jpnprd01.prod.outlook.com>
 <CAOBaU_bZwSHVNVX_v3+_vqmrvAE0gcp6YczWS1kL74LUZ=fMgQ@mail.gmail.com>
 <OSBPR01MB46160EE594D4C0261C0A4B7694490@OSBPR01MB4616.jpnprd01.prod.outlook.com>
 <CAOBaU_bKDoMxEWLqJue8ZS-kamcwKS2zUROONjEtp_sHmbBegg@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

Hi Julien,

I would like to create a link with
https://www.postgresql.org/message-id/1577490124579-0.post@n3.nabble.com

where we met an ASSET FAILURE because query text was not initialized ...

The question raised is:

- should query text be always provided 
or 
- if not how to deal that case (in pgss).

Regards
PAscal



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