Skip site navigation (1) Skip section navigation (2)

Re: How would I "close" a atble?

From: "Tena Sakai" <tsakai(at)gallo(dot)ucsf(dot)edu>
To: "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: <pgsql-admin(at)postgresql(dot)org>
Subject: Re: How would I "close" a atble?
Date: 2007-12-18 07:20:44
Message-ID: FE44E0D7EAD2ED4BB2165071DB8E328C03062E33@egcrc-ex01.egcrc.org (view raw or flat)
Thread:
Lists: pgsql-admin
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
tsakai(at)gallo(dot)ucsf(dot)edu


-----Original Message-----
From: Tom Lane [mailto:tgl(at)sss(dot)pgh(dot)pa(dot)us]
Sent: Mon 12/17/2007 10:43 PM
To: Tena Sakai
Cc: pgsql-admin(at)postgresql(dot)org
Subject: Re: [ADMIN] How would I "close" a atble? 
 
"Tena Sakai" <tsakai(at)gallo(dot)ucsf(dot)edu> 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

In response to

pgsql-admin by date

Next:From: DJ PichayDate: 2007-12-18 08:47:41
Subject: Querying
Previous:From: Tom LaneDate: 2007-12-18 06:43:33
Subject: Re: How would I "close" a atble?

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group