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

Re: Deadlock with pg_dump?

From: "Jim C(dot) Nasby" <jim(at)nasby(dot)net>
To: Chris Campbell <chris(at)bignerdranch(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Deadlock with pg_dump?
Date: 2006-10-26 22:29:11
Message-ID: 20061026222911.GR26892@nasby.net (view raw or flat)
Thread:
Lists: pgsql-hackerspgsql-patches
On Thu, Oct 26, 2006 at 06:11:59PM -0400, Chris Campbell wrote:
> On Oct 26, 2006, at 17:21, Tom Lane wrote:
> 
> >And what was 1171 doing?  I really doubt that either of these could  
> >have
> >been pg_dump.
> 
> I know that process 1120 is a Java client (Hibernate) running an  
> UPDATE query, but I have no idea what 1171 is. I doubt that 1171 was  
> pg_dump, but when we turn off the pg_dump cron jobs (for 12-ish  
> hours), the deadlocks go away. We usually see 5 or 6 deadlocks spread  
> throughout the day. That's not definitive evidence, of course, but  
> it's certainly curious.

I seem to remember something funny about hibernate and locking, though I
can't recall any details right now... but searching the archives might
provide insight.
-- 
Jim Nasby                                            jim(at)nasby(dot)net
EnterpriseDB      http://enterprisedb.com      512.569.9461 (cell)

In response to

pgsql-hackers by date

Next:From: Tom LaneDate: 2006-10-26 22:45:08
Subject: Re: Deadlock with pg_dump?
Previous:From: Andrew SullivanDate: 2006-10-26 22:26:40
Subject: Re: Replication documentation addition

pgsql-patches by date

Next:From: Tom LaneDate: 2006-10-26 22:45:08
Subject: Re: Deadlock with pg_dump?
Previous:From: Chris CampbellDate: 2006-10-26 22:11:59
Subject: Re: Deadlock with pg_dump?

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