From: Sergei Kornilov <sk@zsrv.org>
To: legrand legrand <legrand_legrand@hotmail.com>
To: pgsql-hackers@postgresql.org <pgsql-hackers@postgresql.org>
Subject: Re: pg_stat_statements oddity with track = all
Date: Wed, 02 Dec 2020 17:13:56 +0300
Message-ID: <861161606917332@mail.yandex.ru> (raw)
In-Reply-To: <1606916496022-0.post@n3.nabble.com>
References: <20201202040516.GA43757@nol>
<CANNMO+KrVxMTrzSJLkrkENQX7utVYo1SEyaW54N+Y-Zjew=wbQ@mail.gmail.com>
<20201202063241.GA51769@nol>
<dc48d183-65a2-8f12-3581-ab8f3faeab8b@oss.nttdata.com>
<20201202082402.GB51769@nol>
<1606916496022-0.post@n3.nabble.com>
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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-hackers@postgresql.org
Cc: sk@zsrv.org, legrand_legrand@hotmail.com
Subject: Re: pg_stat_statements oddity with track = all
In-Reply-To: <861161606917332@mail.yandex.ru>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox