Michael Ansley <Michael.Ansley@intec-telecom-systems.com> writes:
> Sorry for my forgetfulness (and a search through geocrawler didn't turn up
> anything useful), but what was the problem with something like NOWAIT?
> e.g.: SELECT * FROM a FOR UPDATE NOWAIT;
> where, if the required lock could not be obtained immediately, this
> statement would raise an error.

I have no objection to that ... it does not cover anything except FOR
UPDATE, though, which is probably less general than some of the other
folks want.

			regards, tom lane

Tue, 17 Apr 2001 12:08:37 -0400
Tom Lane <tgl@sss.pgh.pa.us>
Re: AW: timeout on lock feature 
Sorry for my forgetfulness (and a search through geocrawler didn't turn up
anything useful), but what was the problem with something like NOWAIT?

e.g.: SELECT * FROM a FOR UPDATE NOWAIT;

where, if the required lock could not be obtained immediately, this
statement would raise an error.

Cheers...


MikeA


>> -----Original Message-----
>> From: Tom Lane [mailto:tgl@sss.pgh.pa.us]
>> Sent: 17 April 2001 15:49
>> To: Bruce Momjian
>> Cc: Zeugswetter Andreas SB; Henryk Szal; pgsql-hackers@postgresql.org
>> Subject: Re: AW: [HACKERS] timeout on lock feature 
>> 
>> 
>> Bruce Momjian <pgman@candle.pha.pa.us> writes:
>> > Added to TODO:
>> > 	* Add SET parameter to timeout if waiting for lock too long
>> 
>> I repeat my strong objection to any global (ie, affecting all locks)
>> timeout.  Such a "feature" will have unpleasant consequences.
>> 
>> 			regards, tom lane
>> 
>> ---------------------------(end of 
>> broadcast)---------------------------
>> TIP 5: Have you checked our extensive FAQ?
>> 
>> http://www.postgresql.org/users-lounge/docs/faq.html
>> 


_________________________________________________________________________
This e-mail and any attachments are confidential and may also be privileged and/or copyright 
material of Intec Telecom Systems PLC (or its affiliated companies).  If you are not an 
intended or authorised recipient of this e-mail or have received it in error, please delete 
it immediately and notify the sender by e-mail.  In such a case, reading, reproducing, 
printing or further dissemination of this e-mail is strictly prohibited and may be unlawful. 
Intec Telecom Systems PLC. does not represent or warrant that an attachment hereto is free 
from computer viruses or other defects. The opinions expressed in this e-mail and any 
attachments may be those of the author and are not necessarily those of Intec Telecom 
Systems PLC. 

This footnote also confirms that this email message has been swept by
MIMEsweeper for the presence of computer viruses. 
__________________________________________________________________________





RE: AW: [HACKERS] timeout on lock feature 


Sorry for my forgetfulness (and a search through geocrawler didn't turn up anything useful), but what was the problem with something like NOWAIT?
e.g.: SELECT * FROM a FOR UPDATE NOWAIT;

where, if the required lock could not be obtained immediately, this statement would raise an error.

Cheers...


MikeA


>> -----Original Message-----
>> From: Tom Lane [mailto:tgl@sss.pgh.pa.us]
>> Sent: 17 April 2001 15:49
>> To: Bruce Momjian
>> Cc: Zeugswetter Andreas SB; Henryk Szal; pgsql-hackers@postgresql.org
>> Subject: Re: AW: [HACKERS] timeout on lock feature 
>> 
>> 
>> Bruce Momjian <pgman@candle.pha.pa.us> writes:
>> > Added to TODO:
>> >    * Add SET parameter to timeout if waiting for lock too long
>> 
>> I repeat my strong objection to any global (ie, affecting all locks)
>> timeout.  Such a "feature" will have unpleasant consequences.
>> 
>>                      regards, tom lane
>> 
>> ---------------------------(end of 
>> broadcast)---------------------------
>> TIP 5: Have you checked our extensive FAQ?
>> 
>> http://www.postgresql.org/users-lounge/docs/faq.html
>> 



_________________________________________________________________________
This e-mail and any attachments are confidential and may also be privileged and/or copyright 
material of Intec Telecom Systems PLC (or its affiliated companies).  If you are not an 
intended or authorised recipient of this e-mail or have received it in error, please delete 
it immediately and notify the sender by e-mail.  In such a case, reading, reproducing, 
printing or further dissemination of this e-mail is strictly prohibited and may be unlawful. 
Intec Telecom Systems PLC. does not represent or warrant that an attachment hereto is free 
from computer viruses or other defects. The opinions expressed in this e-mail and any 
attachments may be those of the author and are not necessarily those of Intec Telecom 
Systems PLC. 

This footnote also confirms that this email message has been swept by
MIMEsweeper for the presence of computer viruses. 
__________________________________________________________________________
Tue, 17 Apr 2001 17:09:55 +0100
Michael Ansley <Michael.Ansley@intec-telecom-systems.com>
RE: AW: timeout on lock feature 