Re: pg_stat_statements oddity with track = all

legrand legrand <legrand_legrand@hotmail.com>

From: legrand legrand <legrand_legrand@hotmail.com>
To: pgsql-hackers@postgresql.org
Date: 2020-12-03T08:16:12Z
Lists: pgsql-hackers
Hi Julien,

> The extra field I've proposed would increase the number of records, as it
> needs
to be a part of the key. 

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. Did I miss something ?

Regards
PAscal 



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



Commits

  1. Merge v1.10 of pg_stat_statements into v1.9

  2. Track identical top vs nested queries independently in pg_stat_statements