Re: [FEATURE PATCH] pg_stat_statements with plans (v02)

From: Arthur Zakirov <a(dot)zakirov(at)postgrespro(dot)ru>
To: legrand legrand <legrand_legrand(at)hotmail(dot)com>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: [FEATURE PATCH] pg_stat_statements with plans (v02)
Date: 2018-03-25 21:17:01
Message-ID: 20180325211700.GC19457@arthur.localdomain
Views: Raw Message | Whole Thread | Download mbox
Thread:
Lists: pgsql-hackers

On Thu, Mar 22, 2018 at 11:16:30AM -0700, legrand legrand wrote:
> Reading other pg_stat_statements threads on this forum, there are also activ
> developments to add:
> - planing duration,
> - first date,
> - last_update date,
> - parameters for normalized queries,
> - ...
> as described in
> http://www.postgresql-archive.org/pg-stat-statements-HLD-for-futur-developments-td6012381.html
>
> I was wondering about how would your dev behave with all those new features.
> It seems to me that bad and good plans will not have any of thoses
> informations.

Indeed. I think those developments require cooperation.
Also as you wrote an additional view can be added (pg_stat_statements_plans or pg_stat_plans). But I'm not sure about the name for now and its use cases.

--
Arthur Zakirov
Postgres Professional: http://www.postgrespro.com
Russian Postgres Company

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Damir Simunic 2018-03-25 22:00:35 Re: Proposal: http2 wire format
Previous Message Vladimir Sitnikov 2018-03-25 21:16:08 Re: Backend memory dump analysis