Received: from linux01.aus.de (unknown [62.146.87.130])
	by postgresql.org (Postfix) with ESMTP id E306C475473
	for <pgsql-sql@postgresql.org>; Sun, 21 Jul 2002 20:55:51 -0400 (EDT)
Received: from pd950031c.dip.t-dialin.net ([217.80.3.28] helo=defiant)
	by linux01.aus.de with asmtp (Exim 3.36 #3) id 17WRUR-0007Fk-00
	for pgsql-sql@postgresql.org; Mon, 22 Jul 2002 02:55:55 +0200
From: =?iso-8859-1?Q?Daniel_St=FCwe?= <daniel@aus.de>
To: <pgsql-sql@postgresql.org>
Subject: "no wait" in locks
Date: Mon, 22 Jul 2002 02:50:12 +0200
Message-ID: <000001c23119$d15d20c0$0f64a8c0@aus.de>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.3311
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4910.0300
X-Archive-Number: 200207/325
X-Sequence-Number: 8703

Hi...

anyone knows a workaround for Oracle "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 regard
Daniel Stuewe