Re: Detail part for still waiting for lock log message

From: Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>
To: Tarvi Pillessaar <tarvip(at)gmail(dot)com>
Cc: Peter Eisentraut <peter_e(at)gmx(dot)net>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Detail part for still waiting for lock log message
Date: 2013-08-26 19:20:54
Message-ID: 20130826192054.GB6206@eldon.alvh.no-ip.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Heikki Linnakangas 2013-08-26 19:29:06 pg_restore multiple --function options
Previous Message Dimitri Fontaine 2013-08-26 19:13:49 Re: pg_system_identifier()