Re: reading pg_stat_activity view

Поиск
Список
Период
Сортировка
От Scott Marlowe
Тема Re: reading pg_stat_activity view
Дата
Msg-id dcc563d10712131357g1fbf10e5o1f1b3440a0a71082@mail.gmail.com
обсуждение исходный текст
Ответ на Re: reading pg_stat_activity view  ("Tena Sakai" <tsakai@gallo.ucsf.edu>)
Список pgsql-admin
On Dec 13, 2007 3:43 PM, Tena Sakai <tsakai@gallo.ucsf.edu> wrote:
>
>  My next question:
>  What would be a good way to tell if some
>  query is hung?

That would really depend on what you mean by hung.  Just running a
really long time, or waiting for a lock that some other session is not
will to commit / rollback like above?

I take it you just mean long running queries.  You can do a couple of
things.  You can set the value for statement_timeout and any statement
that takes over that amount of time will generate a timeout and you
then log it in the logs.

You can use pg_stat_activity to see how long a query's been running.
Something like

select datname, usename, current_query, waiting, now() - query_start
from pg_stat_activity order by query_start;

can show you how long each query has been running.

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

Предыдущее
От: Andrew Sullivan
Дата:
Сообщение: Re: Dangerous hint in the PostgreSQL manual
Следующее
От: "Tena Sakai"
Дата:
Сообщение: Re: reading pg_stat_activity view