Devrim GUNDUZ wrote:
Now we have LOCK TABLE ... NOWAIT; but I wonder whether we'll have the
SELECT ... NOWAIT one. Today I got a request for this; and it was
reported that this feature will be used in a huge project.
Well, it shouldn't be too much of a patch - just cloning the code?
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
On Mon, 13 Sep 2004, Simon Riggs wrote:
Now we have LOCK TABLE ... NOWAIT; but I wonder whether we'll have the
SELECT ... NOWAIT one. Today I got a request for this; and it was
reported that this feature will be used in a huge project.
Well, it
Robert Treat...
On Friday 10 September 2004 17:58, Bruce Momjian wrote:
Devrim GUNDUZ wrote:
Hi,
AFAIR there was a thread about SELECT FOR UPDATE NOWAIT
availability in
{7.5,8.0}, 7-8 months ago.
Now we have LOCK TABLE ... NOWAIT; but I wonder whether we'll have the
SELECT
On Friday 10 September 2004 17:58, Bruce Momjian wrote:
Devrim GUNDUZ wrote:
Hi,
AFAIR there was a thread about SELECT FOR UPDATE NOWAIT availability in
{7.5,8.0}, 7-8 months ago.
Now we have LOCK TABLE ... NOWAIT; but I wonder whether we'll have the
SELECT ... NOWAIT one. Today I
Devrim GUNDUZ wrote:
[ PGP not available, raw data follows ]
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
AFAIR there was a thread about SELECT FOR UPDATE NOWAIT availability in
{7.5,8.0}, 7-8 months ago.
Now we have LOCK TABLE ... NOWAIT; but I wonder whether we'll have the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
AFAIR there was a thread about SELECT FOR UPDATE NOWAIT availability in
{7.5,8.0}, 7-8 months ago.
Now we have LOCK TABLE ... NOWAIT; but I wonder whether we'll have the
SELECT ... NOWAIT one. Today I got a request for this; and it was
DB2 8.2 now supports NOWAIT also... Best Regards, Simon Riggs
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Behalf Of Devrim GUNDUZ
Sent: 08 September 2004 23:57
To: [EMAIL PROTECTED]
Subject: [HACKERS] SELECT FOR UPDATE NOWAIT and PostgreSQL 8.0
Paulo Scardine wrote:
LockAcquire has a dontWait parameter, which do just what I want.
The executor level calls heap_open(relid, RowShareLock) when doing
FOR
UPDATEs.
Should we define something like RowShareLockNoWait, so heap_open()
or other
lower level functions can call
Rod Taylor wrote:
-- Start of PGP signed section.
On Fri, 2003-07-18 at 19:46, Paulo Scardine wrote:
My boss is asking for something like Oracle's SELECT FOR UPDATE
NOWAIT.
Is there any such feature? If no, should I look forward into
implementing
this? Any advice?
Lookup
, 2003 4:35 AM
Subject: Re: [HACKERS] SELECT FOR UPDATE NOWAIT
...
Lookup STATEMENT_TIMEOUT and set it to a very short time.
Some people have said they want to distinguish between a slow query
(busy system) and waiting on a lock. I can particulary see wanting to
do a NOWAIT only
Paulo Scardine wrote:
(Excuse my english, my native language is portuguese)
I think I'm a quite attentive to the SQL and HACKERS list, and I see
requests for a NOWAIT option at least once a month, and it's growing.
Regards, Christoph
Yes. I have done a little google about pgsql select
My guess is that we will implement it was a SET variable so it can
control FOR UPDATE/LOCK/UPDATE/DELETE.
Added to TODO:
Add GUC variable to prevent waiting on locks
Interesting.
I have a lot of potentially dumb questions:
- Is this easier to implement as a user variable than in the parser
Paulo Scardine [EMAIL PROTECTED] writes:
- Where is the best place to put this?
I think it would be a really *bad* idea to put it in LockAcquire; that
risks breaking things that you don't want broken.
Whether it's special syntax or a GUC variable, the restriction should
only apply to SELECT FOR
Tom Lane wrote:
Paulo Scardine [EMAIL PROTECTED] writes:
- Where is the best place to put this?
I think it would be a really *bad* idea to put it in LockAcquire; that
risks breaking things that you don't want broken.
Whether it's special syntax or a GUC variable, the restriction should
] SELECT FOR UPDATE NOWAIT
Tom Lane wrote:
Paulo Scardine [EMAIL PROTECTED] writes:
- Where is the best place to put this?
I think it would be a really *bad* idea to put it in LockAcquire; that
risks breaking things that you don't want broken.
Whether it's special syntax or a GUC
Paulo Scardine wrote:
LockAcquire has a dontWait parameter, which do just what I want.
The executor level calls heap_open(relid, RowShareLock) when doing FOR
UPDATEs.
Should we define something like RowShareLockNoWait, so heap_open() or other
lower level functions can call LockAcquire()
Rod Taylor wrote:
-- Start of PGP signed section.
On Fri, 2003-07-18 at 19:46, Paulo Scardine wrote:
My boss is asking for something like Oracle's SELECT FOR UPDATE NOWAIT.
Is there any such feature? If no, should I look forward into implementing
this? Any advice?
Lookup
My boss is asking for something like Oracle's SELECT FOR UPDATE NOWAIT.
Is there any such feature? If no, should I look forward into implementing
this? Any advice?
Thank you,
--
Paulo Scardine
---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system
On Fri, 2003-07-18 at 19:46, Paulo Scardine wrote:
My boss is asking for something like Oracle's SELECT FOR UPDATE NOWAIT.
Is there any such feature? If no, should I look forward into implementing
this? Any advice?
Lookup STATEMENT_TIMEOUT and set it to a very short time.
signature.asc
19 matches
Mail list logo
