pg.ddx.io pgsql-sql@postgresql.org mailing list archivehelp / color / mirror / Atom feed
"no wait" in locks 2+ messages / 1 participants [nested] [flat]
* "no wait" in locks @ 2002-07-22 00:50 Daniel Stüwe <daniel@aus.de> 0 siblings, 0 replies; 2+ messages in thread From: Daniel Stüwe @ 2002-07-22 00:50 UTC (permalink / raw) To: 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 regard Daniel Stuewe ^ permalink raw reply [nested|flat] 2+ messages in thread
* "no wait" in locks @ 2002-07-22 00:54 Daniel Stüwe <daniel@aus.de> 0 siblings, 0 replies; 2+ messages in thread From: Daniel Stüwe @ 2002-07-22 00:54 UTC (permalink / raw) To: 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 ^ permalink raw reply [nested|flat] 2+ messages in thread
end of thread, other threads:[~2002-07-22 00:54 UTC | newest] Thread overview: 2+ messages (download: mbox mbox.gz follow: Atom feed) -- links below jump to the message on this page -- 2002-07-22 00:50 "no wait" in locks Daniel Stüwe <daniel@aus.de> 2002-07-22 00:54 "no wait" in locks Daniel Stüwe <daniel@aus.de>
This inbox is served by DDX for PostgreSQL; see mirroring instructions for how to clone and mirror all data and code used for this inbox