From: Ang Chin Han <angch@bytecraft.com.my>
To: Christoph Haller <ch@rodos.fzk.de>
Cc: pgsql-sql@postgresql.org
Cc: jb@baltic-online.de
Subject: Re: Non-Blocking Locks (i.e. Oracle NOWAIT)
Date: Wed, 16 Jul 2003 11:17:47 +0800
Message-ID: <3F14C3DB.6030501@bytecraft.com.my> (raw)
In-Reply-To: <3F1415B7.9001551F@rodos.fzk.de>
References: <3F1415B7.9001551F@rodos.fzk.de>
Christoph Haller wrote:
> PostgreSQL 7.3.2
> T1: begin; select * from foo for update;
> T2: set STATEMENT_TIMEOUT = 1000; -- milliseconds
Seems like setting it to 1 (ms) emulates the NOWAIT condition better.
Can't set it to 0, though.
> T2: select * from foo for update;
> T2: ERROR: Query was cancelled.
How picky are we in borrowing syntax and idiocyncracies (?) from other
DBs? Since we can closely emulate Oracle's behaviour on SELECT ... FOR
UPDATE NOWAIT, should we just add NOWAIT to the next (non-feature frozen
version) of postgres?
--
Linux homer 2.4.18-14 #1 Wed Sep 4 13:35:50 EDT 2002 i686 i686 i386
GNU/Linux
10:30am up 202 days, 1:35, 6 users, load average: 5.40, 5.14, 5.05
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-sql@postgresql.org
Cc: angch@bytecraft.com.my, ch@rodos.fzk.de, jb@baltic-online.de
Subject: Re: Non-Blocking Locks (i.e. Oracle NOWAIT)
In-Reply-To: <3F14C3DB.6030501@bytecraft.com.my>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
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