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 1huAYy-0002Jf-Qd
	for pgsql-hackers@arkaria.postgresql.org; Sun, 04 Aug 2019 07:04:16 +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 1huAYv-00068t-Of
	for pgsql-hackers@arkaria.postgresql.org; Sun, 04 Aug 2019 07:04:13 +0000
Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29])
	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 1huAYv-0005ti-C8
	for pgsql-hackers@lists.postgresql.org; Sun, 04 Aug 2019 07:04:13 +0000
Received: from n3.nabble.com ([162.255.23.22])
	by magus.postgresql.org with esmtp (Exim 4.89)
	(envelope-from <legrand_legrand@hotmail.com>)
	id 1huAYl-00061H-Rg
	for pgsql-hackers@postgresql.org; Sun, 04 Aug 2019 07:04:11 +0000
Received: from n3.nabble.com (localhost [127.0.0.1])
	by n3.nabble.com (Postfix) with ESMTP id 8099B1608EF66
	for <pgsql-hackers@postgresql.org>; Sun,  4 Aug 2019 00:04:01 -0700 (MST)
Date: Sun, 4 Aug 2019 00:04:01 -0700 (MST)
From: legrand legrand <legrand_legrand@hotmail.com>
To: pgsql-hackers@postgresql.org
Message-ID: <1564902241482-0.post@n3.nabble.com>
In-Reply-To: 
 <CAOBaU_aPixr3sj8Ov7o4eToOdA0f68ZV+Z4drn2LHn4QJTj8Tg@mail.gmail.com>
References: 
 <CAH2-WzmDsNL-vjsBJQ5NRrULyDWBx8YTofr3ZmRfy7As13gQ7A@mail.gmail.com>
 <156456325840.1401.4726441619340285592.pgcf@coridan.postgresql.org>
 <CAOBaU_YEgEiTuQr8O32TqxdoA+mM=owXKe2P1eKM_5XssR1_FQ@mail.gmail.com>
 <20190731215909.xsygisccnirdld3f@alap3.anarazel.de>
 <CAOBaU_bYGuoN8d3WXQ5HufXfkxuL3M=YCWHa33rRRR-fqLFefA@mail.gmail.com>
 <CA+TgmoYyFN3FuiC+E0Ug4ceXmfUYKpmqx6xZdLZq-F9ZJoZutg@mail.gmail.com>
 <20190801183632.7byx3knosxas4ih3@alap3.anarazel.de>
 <CAOBaU_bY3Fx+L_HL4x9pK1+9z8rDt49q=twcvrNi-fxpBdnJgg@mail.gmail.com>
 <20190801210514.qdiam2oazua6otkk@alap3.anarazel.de>
 <CAOBaU_aPixr3sj8Ov7o4eToOdA0f68ZV+Z4drn2LHn4QJTj8Tg@mail.gmail.com>
Subject: Re: Feature improvement: can we add queryId for
 pg_catalog.pg_stat_activity view?
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

>  However having the nested queryid in 
> pg_stat_activity would be convenient to track
> what is a long stored functions currently doing.

+1

And  this could permit to get wait event sampling per queryid when
pg_stat_statements.track = all

Regards 
PAscal



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