Re: Detail part for still waiting for lock log message

Поиск
Список
Период
Сортировка
От Alvaro Herrera
Тема Re: Detail part for still waiting for lock log message
Дата
Msg-id 20130826192054.GB6206@eldon.alvh.no-ip.org
обсуждение исходный текст
Ответ на Re: Detail part for still waiting for lock log message  (Tarvi Pillessaar <tarvip@gmail.com>)
Ответы Re: Detail part for still waiting for lock log message
Список pgsql-hackers
Tarvi Pillessaar escribió:
> Fixed patch attached.

1. this assumes there is only one holder, which is not correct.
(Consider two backends holding shared lock on something and another one
stuck trying to acquire exclusive)

2. I think pgstat_get_backend_current_activity() can be helpful.

3. Doesn't this risk excessive overhead?  Can the other backends be gone
(or done with the lock) before the report has completed?  If this
happens, is there a problem?

-- 
Álvaro Herrera                http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services



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

Предыдущее
От: Dimitri Fontaine
Дата:
Сообщение: Re: pg_system_identifier()
Следующее
От: Heikki Linnakangas
Дата:
Сообщение: pg_restore multiple --function options