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 861161606917332@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
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



pgsql-hackers by date:

Previous
From: yuzuko
Date:
Subject: Re: Autovacuum on partitioned table (autoanalyze)
Next
From: Nikolay Samokhvalov
Date:
Subject: Re: pg_stat_statements oddity with track = all