pg.ddx.io  pgsql-hackers@postgresql.org mailing list archive  

help / color / mirror / Atom feed

From: Sergei Kornilov <sk@zsrv.org>
To: legrand legrand <legrand_legrand@hotmail.com>
To: pgsql-hackers@postgresql.org <pgsql-hackers@postgresql.org>
Subject: Re: pg_stat_statements oddity with track = all
Date: Thu, 03 Dec 2020 11:40:22 +0300
Message-ID: <1110111606984390@mail.yandex.ru> (raw)
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>

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

view thread (32+ messages)  latest in thread

Message-ID: <1110111606984390@mail.yandex.ru>
Permalink:  ../1110111606984390@mail.yandex.ru/
Also on:    postgresql.org/message-id/1110111606984390@mail.yandex.ru

copy link · copy postgr.es

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-hackers@postgresql.org
  Cc: sk@zsrv.org, legrand_legrand@hotmail.com
  Subject: Re: pg_stat_statements oddity with track = all
  In-Reply-To: <1110111606984390@mail.yandex.ru>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox