| From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
|---|---|
| To: | Petr Jelinek <petr(at)2ndquadrant(dot)com>, Peter Geoghegan <pg(at)heroku(dot)com> |
| Cc: | Arne Scheffer <arne(dot)scheffer(at)uni-muenster(dot)de>, David G Johnston <david(dot)g(dot)johnston(at)gmail(dot)com>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Add min and max execute statement time in pg_stat_statement |
| Date: | 2015-02-17 01:57:08 |
| Message-ID: | 54E29FF4.5070304@dunslane.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 02/16/2015 08:48 PM, Petr Jelinek wrote:
> On 17/02/15 01:57, Peter Geoghegan wrote:
>> On Mon, Feb 16, 2015 at 4:44 PM, Petr Jelinek <petr(at)2ndquadrant(dot)com>
>> wrote:
>>> We definitely want this feature, I wished to have this info many times.
>>
>> I would still like to see a benchmark.
>>
>>
>
> Average of 3 runs of read-only pgbench on my system all with
> pg_stat_statement activated:
> HEAD: 20631
> SQRT: 20533
> SQRTD: 20592
>
>
So using sqrtd the cost is 0.18%. I think that's acceptable.
cheers
andrew
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrew Dunstan | 2015-02-17 02:03:45 | Re: Add min and max execute statement time in pg_stat_statement |
| Previous Message | Petr Jelinek | 2015-02-17 01:48:09 | Re: Add min and max execute statement time in pg_stat_statement |