Re: Lock Wait Statistics (next commitfest)

Поиск
Список
Период
Сортировка
От Jaime Casanova
Тема Re: Lock Wait Statistics (next commitfest)
Дата
Msg-id 3073cc9b0907200008ua66c322peaa5dc21156f3db1@mail.gmail.com
обсуждение исходный текст
Ответ на Re: Lock Wait Statistics (next commitfest)  (Mark Kirkwood <markir@paradise.net.nz>)
Ответы Re: Lock Wait Statistics (next commitfest)  (Mark Kirkwood <markir@paradise.net.nz>)
Список pgsql-hackers
On Fri, Jul 17, 2009 at 3:38 AM, Mark Kirkwood<markir@paradise.net.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


В списке pgsql-hackers по дате отправления:

Предыдущее
От: Josh Berkus
Дата:
Сообщение: Re: Review: Revise parallel pg_restore's scheduling heuristic
Следующее
От: Laurent Laborde
Дата:
Сообщение: Re: Higher TOAST compression.