Re: deadlock problem in Ad serving.. - Mailing list pgsql-admin

From Christian Brink
Subject Re: deadlock problem in Ad serving..
Date
Msg-id ENEFIFGGPEDGDJMEMKECGENDGCAA.cb@onsitetech.com
Whole thread Raw
In response to Re: deadlock problem in Ad serving..  (Bhuvan A <bhuvansql@myrealbox.com>)
List pgsql-admin
> > ~~~~~~~~~~~~~~~~~~~~~~
> > Error: DBD::Pg::st execute failed: ERROR:  deadlock detected at
> > /usr/local/perlapache/lib/perl/Banner.pm line 71, <GEN1> line 7.
> > ~~~~~~~~~~~~~~~~~~~~~~
>
> It is a genuine error, occurs while two or more transaction process tries
> to update/delete a same record simultaneously. You can overcome this by
> locking the table in share row exclusive mode also. More details can be
> found in the lock command documentation.

Since your using DBI all you need to do is turn AutoCommit off when you load
DBI and call commits after you verify your transaction succeeded. Turning
off AutoCommit wraps a 'begin transaction' around everything.

More info: http://www.perldoc.com/cpan/DBI.html#Transactions


pgsql-admin by date:

Previous
From: Ron Mayer
Date:
Subject: Re: deadlock problem in Ad serving..
Next
From: Tom Lane
Date:
Subject: Re: deadlock problem in Ad serving..