"no wait" in locks

From: Daniel Stüwe <daniel(at)aus(dot)de>
To: <pgsql-sql(at)postgresql(dot)org>
Subject: "no wait" in locks
Date: 2002-07-22 00:54:17
Message-ID: 000401c2311a$60c09620$0f64a8c0@aus.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-sql

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 regards
Daniel Stuewe

Browse pgsql-sql by date

  From Date Subject
Next Message Daniel Stüwe 2002-07-22 01:10:52 "no wait" option for locks
Previous Message Daniel Stüwe 2002-07-22 00:50:12 "no wait" in locks