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