Re: [FEATURE PATCH] pg_stat_statements with plans

From: David Steele <david(at)pgmasters(dot)net>
To: Julian Markwort <julian(dot)markwort(at)uni-muenster(dot)de>
Cc: 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-03 21:29:24
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: pgsql-hackers

Hi Julian,

On 1/25/17 12:34 PM, Julian Markwort wrote:

> TL:DR;
> We extended the functionality of pg_stat_statements so it can track
> worst and best case execution plans.

pg_stat_statements is an important tool and perhaps one of the most used
core extensions. Any improvements would be greatly welcome by the admin
community, I'm sure.

However, this is a rather large change which could be destabilizing to
the many users of this extension. Even though the patch was posted well
in advance of the last CF it has received little discussion so is
essentially new.

I recommend moving this patch to the 2017-07 CF.


In response to


Browse pgsql-hackers by date

  From Date Subject
Next Message Sven R. Kunze 2017-03-03 21:41:39 adding an immutable variant of to_date
Previous Message David Steele 2017-03-03 21:16:02 Re: [WIP]Vertical Clustered Index (columnar store extension)