Postgres Pro
Downloads
Home   >   mailing lists

Re: pg_stat_statements oddity with track = all - Mailing list pgsql-hackers

From Sergei Kornilov
Subject Re: pg_stat_statements oddity with track = all
Date
Msg-id 1110111606984390@mail.yandex.ru
Whole thread Raw
In response to Re: pg_stat_statements oddity with track = all  (legrand legrand <legrand_legrand@hotmail.com>)
Responses Re: pg_stat_statements oddity with track = all
List pgsql-hackers
Tree view 
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
ofcopypaste errors
 

regards, Sergei

pgsql-hackers by date:

Previous
From: Kyotaro Horiguchi
Date:
Subject: Re: Huge memory consumption on partitioned table with FKs
Next
From: Julien Rouhaud
Date:
Subject: Re: pg_stat_statements oddity with track = all