|From:||Mark Kirkwood <markir(at)paradise(dot)net(dot)nz>|
|Subject:||Re: Lock Wait Statistics (next commitfest)|
|Views:||Raw Message | Whole Thread | Download mbox | Resend email|
Mark Kirkwood wrote:
> Mark Kirkwood wrote:
>> Jaime Casanova wrote:
>>> 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
>>>> is my wait time being spent' - but it hides cases like the one you
>>>> 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...
>> Right - I'll look at adding max (at least) early next week.
> Patch with max(wait time).
> Still TODO
> - amalgamate individual transaction lock waits
> - redo (rather ugly) temporary pg_stat_lock_waits in a form more like
This version has the individual transaction lock waits amalgamated.
Still TODO: redo pg_stat_lock_waits ...
|Next Message||Bruce Momjian||2009-08-09 00:52:22||Re: revised hstore patch|
|Previous Message||Tom Lane||2009-08-08 21:29:06||Re: Split-up ECPG patches|