pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Bob Lunney <bob_lunney@yahoo.com>
To: pgsql-admin@postgresql.org, Kamcheung Sham <csham@computer.org>
Subject: Re: Runaway Locks
Date: Tue, 4 May 2010 09:09:22 -0700 (PDT)
Message-ID: <612199.37100.qm@web39702.mail.mud.yahoo.com> (raw)
In-Reply-To: <EABB6BA9-81D1-4C93-9195-20CB1719EEEE@computer.org>

If you're using Tomcat or some other Java container that does connection management restart it and the lock should go away.

Bob Lunney

--- On Fri, 4/30/10, Kamcheung Sham <csham@computer.org> wrote:

> From: Kamcheung Sham <csham@computer.org>
> Subject: [ADMIN] Runaway Locks
> To: pgsql-admin@postgresql.org
> Date: Friday, April 30, 2010, 9:03 AM
> 
> I was connecting to Postgres 8.3 through JDBC. During my
> unit tests, something when wrong and now leaving with the
> following locks in the db:
> 
> arc_dev=# select locktype, mode, relname,
> virtualtransaction, pid from pg_locks l join pg_class c on
> l.relation = c.oid;           
>                
>                 
> locktype |       mode   
>    |         
> relname           |
> virtualtransaction | pid  
> ----------+------------------+----------------------------+--------------------+------
> 
> relation | AccessShareLock  | pg_locks   
>            
>    | 1/38         
>      | 1816 
> relation | RowShareLock     |
> hibernate_sequences        |
> -1/2091555         | 
>     
> relation | RowExclusiveLock | hibernate_sequences 
>       | -1/2091555     
>    |      
> relation | AccessShareLock  | pg_class_oid_index 
>        | 1/38     
>          | 1816 
> relation | AccessShareLock  |
> pg_class_relname_nsp_index | 1/38       
>        | 1816 
> relation | AccessShareLock  | pg_class   
>            
>    | 1/38         
>      | 1816
> (6 rows)arc_dev=# 
> 
> The locks on 'hibernate_sequences' is causing any update to
> the locked row to hang. There is currently no running
> database client process anymore (as I've restarted by server
> a few times).
> 
> My question is how do i kill the virtual transaction and
> have the locks released?
> 
> Thanks,
> kam
> -- 
> Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-admin
> 


      



view thread (2+ messages)

Message-ID: <612199.37100.qm@web39702.mail.mud.yahoo.com>
Permalink:  ../612199.37100.qm@web39702.mail.mud.yahoo.com/
Also on:    postgresql.org/message-id/612199.37100.qm@web39702.mail.mud.yahoo.com

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-admin@postgresql.org
  Cc: bob_lunney@yahoo.com, csham@computer.org
  Subject: Re: Runaway Locks
  In-Reply-To: <612199.37100.qm@web39702.mail.mud.yahoo.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox