Re: deadlock problem in Ad serving..

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Bhuvan A <bhuvansql(at)myrealbox(dot)com>
Cc: pgsql-admin(at)postgresql(dot)org
Subject: Re: deadlock problem in Ad serving..
Date: 2003-01-20 15:18:10
Message-ID: 3021.1043075890@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

Bhuvan A <bhuvansql(at)myrealbox(dot)com> writes:
>> ~~~~~~~~~~~~~~~~~~~~~~
>> 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.

That will just move his problem somewhere else. I think the only real
answer is to use shorter transactions (one per page, not one per several
pages).

regards, tom lane

In response to

Responses

Browse pgsql-admin by date

  From Date Subject
Next Message Andrew Sullivan 2003-01-20 15:28:07 Re: Installing on Sun machine
Previous Message Zhiqiang Feng 2003-01-20 13:52:16 Re: Stalled post to pgsql-admin