| From: | Simon Riggs <simon(at)2ndquadrant(dot)com> |
|---|---|
| To: | Julian Markwort <julian(dot)markwort(at)uni-muenster(dot)de> |
| 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-01-25 17:43:53 |
| Message-ID: | CANP8+j+=h306tyTYaX6ny781HSaddL3+y8jKcuzAvUD5E7Pd4w@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 25 January 2017 at 17:34, Julian Markwort
<julian(dot)markwort(at)uni-muenster(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2017-01-25 17:46:55 | Re: logical-replication.sgml improvements |
| Previous Message | Julian Markwort | 2017-01-25 17:34:49 | [FEATURE PATCH] pg_stat_statements with plans |