Re: pg_stat_statements oddity with track = all

Hello

> - add a parent_statement_id column that would be NULL for top level queries

Will generate too much entries... Every FK for each different delete/insert, for example.
But very useful for databases with a lot of stored procedures to find where this query is called. May be new mode track
=tree? Use NULL to indicate a top-level query (same as with track=tree) and some constant for any nested queries when
track= all.
 

Also, currently a top statement will account buffers usage for underlying statements?

regards, Sergei