Re: deadlock problem in Ad serving..

Hi,

Guys thanks for the response..

I am using perl DBI.

In fact i have tried doing the commit immediately
after the update in the script then i saw my pg_stat_activity
reporting lots of queued update transactions.

I would like to discuss this problem further but not
able to do so at the moment. I have temporarily disabled impression
counting.

I am very thankful to you guys  for the
interest / response once again and will keep you posted.


regds
mallah.




On Monday 20 January 2003 08:48 pm, Tom Lane wrote:
> 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
>
> ---------------------------(end of broadcast)---------------------------
> TIP 2: you can get off all lists at once with the unregister command
>     (send "unregister YourEmailAddressHere" to majordomo@postgresql.org)

--
Rajesh Kumar Mallah,
Project Manager (Development)
Infocom Network Limited, New Delhi
phone: +91(11)6152172 (221) (L) ,9811255597 (M)

Visit http://www.trade-india.com ,
India's Leading B2B eMarketplace.