Re: obtaining row locking information

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>
Cc: Tatsuo Ishii <t-ishii(at)sra(dot)co(dot)jp>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: obtaining row locking information
Date: 2005-08-08 15:35:17
Message-ID: 28769.1123515317@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> writes:
> All in all, Tatsuo is right in that there's no way to know what tuples
> are locked without scanning the whole table.

Sure. I was just questioning how much one needs to know that. It seems
to me that the only time you really care is when you are investigating
a hangup, and then you can get useful info from pg_locks.

regards, tom lane

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Joshua D. Drake 2005-08-08 16:12:02 Re: shrinking the postgresql.conf
Previous Message Alvaro Herrera 2005-08-08 14:46:38 Re: obtaining row locking information