Re: [HACKERS] SELECT FOR UPDATE NOWAIT and PostgreSQL 8.0

2004-09-15 Thread Bruce Momjian
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

Re: [HACKERS] SELECT FOR UPDATE NOWAIT and PostgreSQL 8.0

2004-09-14 Thread Devrim GUNDUZ
-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 sho

Re: [HACKERS] SELECT FOR UPDATE NOWAIT and PostgreSQL 8.0

2004-09-13 Thread Simon Riggs
>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

Re: [HACKERS] SELECT FOR UPDATE NOWAIT and PostgreSQL 8.0

2004-09-12 Thread 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 ... NOWAI

Re: [HACKERS] SELECT FOR UPDATE NOWAIT and PostgreSQL 8.0

2004-09-10 Thread Bruce Momjian
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

Re: [HACKERS] SELECT FOR UPDATE NOWAIT and PostgreSQL 8.0

2004-09-08 Thread Simon Riggs
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

[HACKERS] SELECT FOR UPDATE NOWAIT and PostgreSQL 8.0

2004-09-08 Thread Devrim GUNDUZ
-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 report

Re: [HACKERS] SELECT FOR UPDATE NOWAIT

2003-07-23 Thread Christoph Haller
> > 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 > > UPDATE"s. > > Should we define something like RowShareLockNoWait, so heap_open() or other > > lower level functions

Re: [HACKERS] SELECT FOR UPDATE NOWAIT

2003-07-23 Thread Bruce Momjian
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 > UPDATE"s. > Should we define something like RowShareLockNoWait, so heap_open() or other > lower level functions can call LockAc

Re: [HACKERS] SELECT FOR UPDATE NOWAIT

2003-07-23 Thread Paulo Scardine
ECTED]>; <[EMAIL PROTECTED]> Sent: Wednesday, July 23, 2003 4:30 PM Subject: Re: [HACKERS] SELECT FOR UPDATE NOWAIT > Tom Lane wrote: > > "Paulo Scardine" <[EMAIL PROTECTED]> writes: > > > - Where is the best place to put this? > > >

Re: [HACKERS] SELECT FOR UPDATE NOWAIT

2003-07-23 Thread Bruce Momjian
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 restricti

Re: [HACKERS] SELECT FOR UPDATE NOWAIT

2003-07-23 Thread Tom Lane
"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

Re: [HACKERS] SELECT FOR UPDATE NOWAIT

2003-07-23 Thread Paulo Scardine
> 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 p

Re: [HACKERS] SELECT FOR UPDATE NOWAIT

2003-07-23 Thread Bruce Momjian
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 "pgs

Re: [HACKERS] SELECT FOR UPDATE NOWAIT

2003-07-23 Thread Paulo Scardine
;Christoph Haller" <[EMAIL PROTECTED]> Sent: Wednesday, July 23, 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 que

Re: [HACKERS] SELECT FOR UPDATE NOWAIT

2003-07-23 Thread Christoph Haller
> > 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

Re: [HACKERS] SELECT FOR UPDATE NOWAIT

2003-07-21 Thread Bruce Momjian
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 S

Re: [HACKERS] SELECT FOR UPDATE NOWAIT

2003-07-18 Thread Rod Taylor
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.as

[HACKERS] SELECT FOR UPDATE NOWAIT

2003-07-18 Thread Paulo Scardine
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 (http://www.grisoft.com