| From: | Andres Freund <andres(at)anarazel(dot)de> |
|---|---|
| To: | Julian Markwort <julian(dot)markwort(at)uni-muenster(dot)de> |
| Cc: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>, Simon Riggs <simon(at)2ndquadrant(dot)com>, David Steele <david(at)pgmasters(dot)net>, 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: [HACKERS] [FEATURE PATCH] pg_stat_statements with plans (v02) |
| Date: | 2018-03-01 18:43:02 |
| Message-ID: | 20180301184302.v26c4545jq66wwo6@alap3.anarazel.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi,
On 2018-01-10 15:05:39 +0100, Julian Markwort wrote:
> I'd like to follow up to my previous proposition of tracking (some) best and
> worst plans for different queries in the pg_stat_statements extension.
Cool feature.
I think the patch probably doesn't apply anymore, due to other changes
to pg_stat_statements since its posting. Could you refresh?
I've not done any sort of review. Scrolling through I noticed //
comments which aren't pg coding style.
I'd like to see a small benchmark showing the overhead of the feature.
Both in runtime and storage size.
Greetings,
Andres Freund
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2018-03-01 18:54:55 | Re: Protect syscache from bloating with negative cache entries |
| Previous Message | Peter Geoghegan | 2018-03-01 18:41:51 | Re: 2018-03 Commitfest Summary (Andres #1) |