On Fri, Jul 17, 2009 at 3:38 AM, Mark Kirkwood<markir(at)paradise(dot)net(dot)nz> wrote:
> With respect to the sum of wait times being not very granular, yes - quite
> true. I was thinking it is useful to be able to answer the question 'where
> is my wait time being spent' - but it hides cases like the one you mention.
> What would you like to see? would max and min wait times be a useful
> addition, or are you thinking along different lines?
track number of locks, sum of wait times, max(wait time).
but actually i started to think that the best is just make use of
log_lock_waits send the logs to csvlog and analyze there...
Soporte y capacitación de PostgreSQL
Asesoría y desarrollo de sistemas
Guayaquil - Ecuador
In response to
pgsql-hackers by date
|Next:||From: Jeremy Kerr||Date: 2009-07-20 07:14:02|
|Subject: Re: [PATCH 1/2 v3] [libpq] rework sigpipe-handling macros|
|Previous:||From: Jaime Casanova||Date: 2009-07-20 06:58:56|
|Subject: Re: fix: plpgsql: return query and dropped columns problem|