Re: [HACKERS] pg_stat_activity.waiting_start

Поиск
Список
Период
Сортировка
От Joel Jacobson
Тема Re: [HACKERS] pg_stat_activity.waiting_start
Дата
Msg-id CAASwCXfkxWh0W3aS7qC8Tk7-eEafxN1smhUoqe03fnJxyZ-2VQ@mail.gmail.com
обсуждение исходный текст
Ответ на [HACKERS] pg_stat_activity.waiting_start  (Joel Jacobson <joel@trustly.com>)
Список pgsql-hackers
Actually, "wait_start" is a better name to match the others
("wait_event_type" and "wait_event").


On Sat, Dec 24, 2016 at 8:20 AM, Joel Jacobson <joel@trustly.com> wrote:
> Hi hackers,
>
> We already have xact_start, query_start and backend_start
> to get the timestamptz for when different things happened.
>
> I would like to propose adding a fourth such column, "waiting_start",
> which would tell how long time a backend has been waiting.
>
> The column would be NULL when waiting=FALSE.
>
> While it's trivial to write a script that just polls pg_stat_activity
> every second and keeps tack of when a backend started
> waiting by just checking for any new waiting=TRUE rows,
> it would be more convenient to just get the information from
> pg_stat_activity directly.
>
> The use-case would be e.g. monitoring tools
> when you want to know how long time queries are waiting.
>
> --
> Joel Jacobson



-- 
Joel Jacobson

Mobile: +46703603801
Trustly.com | Newsroom | LinkedIn | Twitter



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

Предыдущее
От: Joel Jacobson
Дата:
Сообщение: [HACKERS] pg_stat_activity.waiting_start
Следующее
От: Tom Lane
Дата:
Сообщение: Re: [HACKERS] pg_stat_activity.waiting_start