Re: deadlock problem in Ad serving..

From: "Rajesh Kumar Mallah(dot)" <mallah(at)trade-india(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 13:39:36
Message-ID: 200301201909.36169.mallah@trade-india.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

thanks for ur response bhuvan,
i will read that doc and try it again.

regds
mallah.

On Monday 20 January 2003 03:32 pm, Bhuvan A wrote:
> > ~~~~~~~~~~~~~~~~~~~~~~
> > 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.
>
> regards,
> bhuvaneswaran
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 1: subscribe and unsubscribe commands go to majordomo(at)postgresql(dot)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.

In response to

Browse pgsql-admin by date

  From Date Subject
Next Message shreedhar 2003-01-20 13:41:23 Triggers taking much time to insert data
Previous Message Zhiqiang Feng 2003-01-20 12:12:34