Re: Detail part for still waiting for lock log message - Mailing list pgsql-hackers

From Alvaro Herrera
Subject Re: Detail part for still waiting for lock log message
Date
Msg-id 20130826192054.GB6206@eldon.alvh.no-ip.org
Whole thread Raw
In response to Re: Detail part for still waiting for lock log message  (Tarvi Pillessaar <tarvip@gmail.com>)
Responses Re: Detail part for still waiting for lock log message  (Tarvi Pillessaar <tarvip@gmail.com>)
List 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 by date:

Previous
From: Dimitri Fontaine
Date:
Subject: Re: pg_system_identifier()
Next
From: Heikki Linnakangas
Date:
Subject: pg_restore multiple --function options