Re: Add min and max execute statement time in pg_stat_statement - Mailing list pgsql-hackers

From Simon Riggs
Subject Re: Add min and max execute statement time in pg_stat_statement
Date
Msg-id CA+U5nMLS3mqs7wJwLyQZBOQeFRvgfGR=T0u-syp-ui7sW2roXA@mail.gmail.com
Whole thread Raw
In response to Re: Add min and max execute statement time in pg_stat_statement  (KONDO Mitsumasa <kondo.mitsumasa@lab.ntt.co.jp>)
List pgsql-hackers
On 23 January 2014 12:43, KONDO Mitsumasa <kondo.mitsumasa@lab.ntt.co.jp> wrote:

> I tested my patch in pgbench, but I cannot find bottleneck of my latest
> patch.
...
> Attached is latest developping patch. It hasn't been test much yet, but sqrt
> caluclation may be faster.

Thank you for reworking this so that the calculation happens outside the lock.

Given your testing, and my own observation that the existing code
could be reworked to avoid contention if people become concerned, I
think this is now ready for commit, as soon as the last point about
Windows is answered.

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



pgsql-hackers by date:

Previous
From: Mitsumasa KONDO
Date:
Subject: Re: Add min and max execute statement time in pg_stat_statement
Next
From: Simon Riggs
Date:
Subject: Re: plpgsql.warn_shadow