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

From Peter Geoghegan
Subject Re: Add min and max execute statement time in pg_stat_statement
Date
Msg-id CAM3SWZR114p8=_nZEy8K-mSYUziTTGaque31CVcGam8sbuoMRQ@mail.gmail.com
Whole thread Raw
In response to Re: Add min and max execute statement time in pg_stat_statement  (Gavin Flower <GavinFlower@archidevsys.co.nz>)
List pgsql-hackers
On Wed, Oct 23, 2013 at 5:15 PM, Gavin Flower
<GavinFlower@archidevsys.co.nz> wrote:
> Anyhow, I was suggesting the faclity be off by default - I see no point in
> enabling where people don't need it, even if the resource RAM, processor,
> whatever, were minimal.

As long as any new field in the Counters struct needs to be protected
by a spinlock, I will be suspicious of the cost. The track_io_timing
stuff is still protected, even when it's turned off. So I'm afraid
that it isn't that simple.

-- 
Peter Geoghegan



pgsql-hackers by date:

Previous
From: Gavin Flower
Date:
Subject: Re: Add min and max execute statement time in pg_stat_statement
Next
From: Tom Lane
Date:
Subject: Re: RULE regression test fragility?