Message-ID: <62532.203.196.138.236.1027308385.squirrel@mail.trade-india.com>
Date: Mon, 22 Jul 2002 08:56:25 +0530 (IST)
Subject: Re: 'no wait' option for locks
From: <mallah@trade-india.com>
To: <pgsql@aus.de>
In-Reply-To: <000801c2311c$b37bde40$0f64a8c0@aus.de>
References: <000801c2311c$b37bde40$0f64a8c0@aus.de>
Importance: Normal
Cc: <pgsql-sql@postgresql.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit

Hi,

Why not the program create a lock file on start and delete it when finished.

regds
mallah.


> Hi...
>
> anyone knows a workaround for Oracles "no wait" option in "SELECT ...
> FOR UPDATE"?
>
> I wrote a programm which runs twice. Both poll the pgsql database all 5
> seconds and make an "SELECT ... FOR UPDATE" for the first row found.
> After some work and commit the next row is processed. The second task
> waits until the first hast commited, but it should detect the lock and
> continue work with next row.
>
> How can i detect this lock? Oracle returns with "no wait" option an sql
> error code.
>
> Any hints?
>
> best regards
> Daniel Stuewe
>
>
> ---------------------------(end of
> broadcast)--------------------------- TIP 6: Have you searched our list
> archives?
>
> http://archives.postgresql.org


-----------------------------------------
Get your free web based email at trade-india.com.
   "India's Leading B2B eMarketplace.!"
http://www.trade-india.com/