Re: pg_stat_statements oddity with track = all

From: legrand legrand <legrand_legrand(at)hotmail(dot)com>
To: pgsql-hackers(at)postgresql(dot)org
Subject: Re: pg_stat_statements oddity with track = all
Date: 2020-12-02 13:41:36
Message-ID: 1606916496022-0.post@n3.nabble.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi,

a crazy idea:
- add a parent_statement_id column that would be NULL for top level queries
- build statement_id for nested queries based on the merge of:
a/ current_statement_id and parent one
or
b/ current_statement_id and nested level.

this would offer the ability to track counters at any depth level ;o)
Regards
PAscal

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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Simon Riggs 2020-12-02 13:46:04 Re: Huge memory consumption on partitioned table with FKs
Previous Message Ian Lawrence Barwick 2020-12-02 13:36:16 Re: proposal: function pg_setting_value_split() to parse shared_preload_libraries etc.