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

Re: Deadlock on transaction

From: Scott Marlowe <smarlowe(at)g2switchworks(dot)com>
To: Ezequias Rodrigues da Rocha <ezequias(dot)rocha(at)gmail(dot)com>
Cc: pgsql-sql(at)postgresql(dot)org, pgsql-admin(at)postgresql(dot)org
Subject: Re: Deadlock on transaction
Date: 2007-02-12 17:48:08
Message-ID: 1171302488.3565.15.camel@state.g2switchworks.com (view raw or flat)
Thread:
Lists: pgsql-adminpgsql-sql
On Mon, 2007-02-12 at 11:43, Ezequias Rodrigues da Rocha wrote:
> Hi list,
> 
> I am curious becouse I am seen my postgresql locking the transactions
> when i load a huge (in some case not to huge) numbers of records
> 70,000 records.
> 
> Could someone help me with it ?

Are sure that what you're speaking of is a deadlock?  Or is it just a
stalled transaction while one one transaction waits for another to
complete?

A true deadlock means that two transactions are stalled waiting for the
other to complete, and neither ever can complete, and they are
DEADlocked.

If you've just got a problem where an update is stalling all the other
transactions, then give us a test case / example code of what's
happening.

If you've got a real deadlock that postgresql isn't catching, that's a
much more serious problem.

In response to

Responses

pgsql-admin by date

Next:From: Ezequias Rodrigues da RochaDate: 2007-02-12 18:08:27
Subject: Re: Deadlock on transaction
Previous:From: Ezequias Rodrigues da RochaDate: 2007-02-12 17:43:14
Subject: Deadlock on transaction

pgsql-sql by date

Next:From: Ezequias Rodrigues da RochaDate: 2007-02-12 18:08:27
Subject: Re: Deadlock on transaction
Previous:From: Ezequias Rodrigues da RochaDate: 2007-02-12 17:43:14
Subject: Deadlock on transaction

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