Re: [FEATURE PATCH] pg_stat_statements with plans

From: Julian Markwort <julian(dot)markwort(at)uni-muenster(dot)de>
To: Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>, Simon Riggs <simon(at)2ndquadrant(dot)com>
Cc: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>, marius(dot)timmer(at)uni-muenster(dot)de, arne(dot)scheffer(at)uni-muenster(dot)de
Subject: Re: [FEATURE PATCH] pg_stat_statements with plans
Date: 2017-03-04 13:56:13
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: pgsql-hackers

Alright, for the next version of this patch I'll look into standard
deviation (an implementation of Welfords' algorithm already exists in

On 3/4/17 14:18, Peter Eisentraut wrote:

> The other problem is that this measures execution time, which can vary
> for reasons other than plan. I would have expected that the cost
> numbers are tracked somehow.
I've already thought of tracking specific parts of the explanation, like
the cost numbers, instead of the whole string, I'll think of something,
but if anybody has any bright ideas in the meantime, I'd gladly listen
to them.

> There is also the issue of generic vs specific plans, which this
> approach might be papering over.
Would you be so kind and elaborate a little bit on this? I'm not sure if
I understand this correctly. This patch only tracks specific plans, yes.
The inital idea was that there might be some edge-cases that are not
apparent when looking at generalized plans or queries.

kind regards

In response to


Browse pgsql-hackers by date

  From Date Subject
Next Message Stephen Frost 2017-03-04 14:00:04 Re: Cost model for parallel CREATE INDEX
Previous Message David Steele 2017-03-04 13:48:19 Re: [FEATURE PATCH] pg_stat_statements with plans