| From: | Jaime Casanova <jcasanov(at)systemguards(dot)com(dot)ec> |
|---|---|
| To: | Mark Kirkwood <markir(at)paradise(dot)net(dot)nz> |
| Cc: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Lock Wait Statistics (next commitfest) |
| Date: | 2009-07-20 07:08:57 |
| Message-ID: | 3073cc9b0907200008ua66c322peaa5dc21156f3db1@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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...
--
Atentamente,
Jaime Casanova
Soporte y capacitación de PostgreSQL
Asesoría y desarrollo de sistemas
Guayaquil - Ecuador
Cel. +59387171157
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jeremy Kerr | 2009-07-20 07:14:02 | Re: [PATCH 1/2 v3] [libpq] rework sigpipe-handling macros |
| Previous Message | Jaime Casanova | 2009-07-20 06:58:56 | Re: fix: plpgsql: return query and dropped columns problem |