Re: [HACKERS] [FEATURE PATCH] pg_stat_statements with plans - Mailing list pgsql-hackers

From Simon Riggs
Subject Re: [HACKERS] [FEATURE PATCH] pg_stat_statements with plans
Date
Msg-id CANP8+j+=h306tyTYaX6ny781HSaddL3+y8jKcuzAvUD5E7Pd4w@mail.gmail.com
Whole thread Raw
In response to [HACKERS] [FEATURE PATCH] pg_stat_statements with plans  (Julian Markwort <julian.markwort@uni-muenster.de>)
Responses Re: [HACKERS] [FEATURE PATCH] pg_stat_statements with plans  (Peter Eisentraut <peter.eisentraut@2ndquadrant.com>)
List pgsql-hackers
On 25 January 2017 at 17:34, Julian Markwort
<julian.markwort@uni-muenster.de> wrote:

> Analogous to this, a bad_plan is saved, when the time has been exceeded by a
> factor greater than 1.1 .

...and the plan differs?

Probably best to use some stat math to calculate deviation, rather than fixed %.

Sounds good.

-- 
Simon Riggs                http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services



pgsql-hackers by date:

Previous
From: Julian Markwort
Date:
Subject: [HACKERS] [FEATURE PATCH] pg_stat_statements with plans
Next
From: Peter Eisentraut
Date:
Subject: Re: [HACKERS] logical-replication.sgml improvements