Hi Tom,
Here it is!
locktype | relation | transactionid | transaction | mode
| pid | granted
---------------+----------+---------------+-------------+---------------------+--------+---------
relation | 16496 | | 147195029 | AccessShareLock
| 22833 | t
I kept looking at the ones I emailed to you which
omitted a few rows from the bottom. That was dumb!
I issued "kill -INT 22833" and in a few minutes
pg_locks view shrunk to 2 rows from 41 rows.
Many thanks for following up with this problem.
Regards,
Tena Sakai
[EMAIL PROTECTED]
-----Original Message-----
From: Tom Lane [mailto:[EMAIL PROTECTED]
Sent: Mon 12/17/2007 10:43 PM
To: Tena Sakai
Cc: pgsql-admin@postgresql.org
Subject: Re: [ADMIN] How would I "close" a atble?
"Tena Sakai" <[EMAIL PROTECTED]> writes:
>> What you have not shown us is what transaction has
>> actually *got* a lock on 16496.
> Would you mind enlightening me as to how I can do so?
Are there no other rows in pg_locks that reference relation 16496?
None of the ones you showed us had granted=t, but there must be one
unless things are much more broken than I think.
regards, tom lane
