Re: pg_stat_statements oddity with track = all

From: Sergei Kornilov <sk(at)zsrv(dot)org>
To: legrand legrand <legrand_legrand(at)hotmail(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: pg_stat_statements oddity with track = all
Date: 2020-12-03 08:40:22
Message-ID: 1110111606984390@mail.yandex.ru
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Julien Rouhaud 2020-12-03 08:52:08 Re: pg_stat_statements oddity with track = all
Previous Message Kyotaro Horiguchi 2020-12-03 08:27:02 Re: Huge memory consumption on partitioned table with FKs