| From: | "Christian Brink" <cb(at)onsitetech(dot)com> |
|---|---|
| To: | "Bhuvan A" <bhuvansql(at)myrealbox(dot)com>, <pgsql-admin(at)postgresql(dot)org> |
| Subject: | Re: deadlock problem in Ad serving.. |
| Date: | 2003-01-20 17:48:33 |
| Message-ID: | ENEFIFGGPEDGDJMEMKECGENDGCAA.cb@onsitetech.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Ron Mayer | 2003-01-20 17:58:10 | Re: deadlock problem in Ad serving.. |
| Previous Message | Zhiqiang Feng | 2003-01-20 16:34:40 |