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 <pgsql-hackers-owner+archive@lists.postgresql.org>)
	id 1kkkAD-0003a2-W0
	for pgsql-hackers@arkaria.postgresql.org; Thu, 03 Dec 2020 08:40:34 +0000
Received: from localhost ([127.0.0.1] helo=malur.postgresql.org)
	by malur.postgresql.org with esmtp (Exim 4.92)
	(envelope-from <pgsql-hackers-owner+archive@lists.postgresql.org>)
	id 1kkkAC-0001bD-UG
	for pgsql-hackers@arkaria.postgresql.org; Thu, 03 Dec 2020 08:40:32 +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 <sk@zsrv.org>)
	id 1kkkAC-0001b5-IZ
	for pgsql-hackers@lists.postgresql.org; Thu, 03 Dec 2020 08:40:32 +0000
Received: from forward501p.mail.yandex.net ([77.88.28.111])
	by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256)
	(Exim 4.92)
	(envelope-from <sk@zsrv.org>)
	id 1kkkA7-0002Un-08
	for pgsql-hackers@postgresql.org; Thu, 03 Dec 2020 08:40:31 +0000
Received: from mxback22j.mail.yandex.net (mxback22j.mail.yandex.net
 [IPv6:2a02:6b8:c04:242:0:640:a4b3:d951])
	by forward501p.mail.yandex.net (Yandex) with ESMTP id 8144D35009C3;
	Thu,  3 Dec 2020 11:40:23 +0300 (MSK)
Received: from localhost (localhost [::1])
	by mxback22j.mail.yandex.net (mxback/Yandex) with ESMTP id
 eLVDp7XYPq-eMPenCWG;
	Thu, 03 Dec 2020 11:40:22 +0300
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=zsrv.org; s=mail;
 t=1606984822;
	bh=R9VeYGO8Jr9h4DepHUaDHL55ORQXkL9mllHDMudtxxM=;
	h=References:Date:Message-Id:Subject:In-Reply-To:To:From;
	b=d47HmYIeFJPidVHM8JRbNTzZWSB6DhJX7r+PNRxEOAruFROV7wD7nCYLtc1NPP1D/
	 R6qKSlxfa25XffCK0mNVmBweyNVOipg1r3PkegiJH0UZGx5IiGG8wSWH+idxHSCGwN
	 znwBaMFDu7sjgOS9Bp/hyaXamU4RUgTUK9oa4p5Q=
Authentication-Results: mxback22j.mail.yandex.net;
 dkim=pass header.i=@zsrv.org
Received: by myt5-07963c3d6ee6.qloud-c.yandex.net with HTTP;
	Thu, 03 Dec 2020 11:40:22 +0300
From: Sergei Kornilov <sk@zsrv.org>
To: legrand legrand <legrand_legrand@hotmail.com>,
	"pgsql-hackers@postgresql.org" <pgsql-hackers@postgresql.org>
In-Reply-To: <1606983372910-0.post@n3.nabble.com>
References: <20201202040516.GA43757@nol>
 <CANNMO+KrVxMTrzSJLkrkENQX7utVYo1SEyaW54N+Y-Zjew=wbQ@mail.gmail.com>
 <20201202063241.GA51769@nol>
 <CANNMO++VRu2r17jqxBDFZF4++p+f4WE+VbvOPAQi_4BTwP4g=Q@mail.gmail.com>
 <20201203010051.GA8050@nol> <1606983372910-0.post@n3.nabble.com>
Subject: Re: pg_stat_statements oddity with track = all
MIME-Version: 1.0
X-Mailer: Yamail [ http://yandex.ru ] 5.0
Date: Thu, 03 Dec 2020 11:40:22 +0300
Message-Id: <1110111606984390@mail.yandex.ru>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain
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

Hello

> To get an increase in the number of records that means that the same
> statement
> would appear at top level AND nested level. This seems a corner case with
> very low
> (neglectible) occurence rate.

+1
I think splitting fields into plans_toplevel / plans_nested will be less convenient. And more code with higher chance of copypaste errors

regards, Sergei