Re: [COMMITTERS] pgsql: Provide much better wait information in pg_stat_activity.

Поиск
Список
Период
Сортировка
От Pavel Stehule
Тема Re: [COMMITTERS] pgsql: Provide much better wait information in pg_stat_activity.
Дата
Msg-id CAFj8pRAjRzmdi6_NBfkQgZefbJ2s+i8g=us79GzCy9YQ=puLmg@mail.gmail.com
обсуждение исходный текст
Ответ на Re: [COMMITTERS] pgsql: Provide much better wait information in pg_stat_activity.  (Robert Haas <robertmhaas@gmail.com>)
Ответы Re: [COMMITTERS] pgsql: Provide much better wait information in pg_stat_activity.  (Robert Haas <robertmhaas@gmail.com>)
Список pgsql-hackers


2016-03-10 22:24 GMT+01:00 Robert Haas <robertmhaas@gmail.com>:

rhaas=# select query, state, wait_event, wait_event_type from pg_stat_activity;
                                  query
  | state  |  wait_event   | wait_event_type
-------------------------------------------------------------------------+--------+---------------+-----------------
 select query, state, wait_event, wait_event_type from
pg_stat_activity; | active |               |
 select * from foo for update;
  | active | transactionid | Lock
(2 rows)

...which looks right to me.

> session two:
> rollback; begin; select * from foo where a = 10 for update;
> session two is waiting again

I don't see how you can do this here - the session is blocked.

There could well be a bug here, but I need a little more help to find it.

Maybe it be clear from attached text file

Regards

 

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

Вложения

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

Предыдущее
От: "Regina Obe"
Дата:
Сообщение: Re: Is there a way around function search_path killing SQL function inlining? - and backup / restore issue
Следующее
От: Robert Haas
Дата:
Сообщение: Re: [COMMITTERS] pgsql: Provide much better wait information in pg_stat_activity.