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

From Tom Lane
Subject Re: deadlock problem in Ad serving..
Date
Msg-id 3021.1043075890@sss.pgh.pa.us
Whole thread Raw
In response to Re: deadlock problem in Ad serving..  (Bhuvan A <bhuvansql@myrealbox.com>)
Responses Re: deadlock problem in Ad serving..  (Ron Mayer <ron@intervideo.com>)
Re: deadlock problem in Ad serving..  ("Rajesh Kumar Mallah." <mallah@trade-india.com>)
List pgsql-admin
Bhuvan A <bhuvansql@myrealbox.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

pgsql-admin by date:

Previous
From: "shreedhar"
Date:
Subject: Triggers taking much time to insert data
Next
From: Andrew Sullivan
Date:
Subject: Re: Installing on Sun machine