RE: AW: timeout on lock feature - Mailing list pgsql-hackers
From | Michael Ansley |
---|---|
Subject | RE: AW: timeout on lock feature |
Date | |
Msg-id | 7F124BC48D56D411812500D0B747251480F52E@fileserver002.intecsystems.co.uk Whole thread Raw |
In response to | AW: timeout on lock feature (Zeugswetter Andreas SB <ZeugswetterA@wien.spardat.at>) |
Responses |
Re: AW: timeout on lock feature
|
List | pgsql-hackers |
<p><font size="2">Sorry for my forgetfulness (and a search through geocrawler didn't turn up anything useful), but what wasthe problem with something like NOWAIT?</font><p><font size="2">e.g.: SELECT * FROM a FOR UPDATE NOWAIT;</font><p><fontsize="2">where, if the required lock could not be obtained immediately, this statement would raisean error.</font><p><font size="2">Cheers...</font><br /><p><font size="2">MikeA</font><br /><p><font size="2">>>-----Original Message-----</font><br /><font size="2">>> From: Tom Lane [<a href="mailto:tgl@sss.pgh.pa.us">mailto:tgl@sss.pgh.pa.us</a>]</font><br/><font size="2">>> Sent: 17 April 2001 15:49</font><br/><font size="2">>> To: Bruce Momjian</font><br /><font size="2">>> Cc: Zeugswetter Andreas SB;Henryk Szal; pgsql-hackers@postgresql.org</font><br /><font size="2">>> Subject: Re: AW: [HACKERS] timeout on lockfeature </font><br /><font size="2">>> </font><br /><font size="2">>> </font><br /><font size="2">>>Bruce Momjian <pgman@candle.pha.pa.us> writes:</font><br /><font size="2">>> > Added to TODO:</font><br/><font size="2">>> > * Add SET parameter to timeout if waiting for lock too long</font><br /><fontsize="2">>> </font><br /><font size="2">>> I repeat my strong objection to any global (ie, affecting alllocks)</font><br /><font size="2">>> timeout. Such a "feature" will have unpleasant consequences.</font><br /><fontsize="2">>> </font><br /><font size="2">>> regards, tom lane</font><br /><font size="2">>></font><br /><font size="2">>> ---------------------------(end of </font><br /><font size="2">>>broadcast)---------------------------</font><br /><font size="2">>> TIP 5: Have you checked our extensiveFAQ?</font><br /><font size="2">>> </font><br /><font size="2">>> <a href="http://www.postgresql.org/users-lounge/docs/faq.html" target="_blank">http://www.postgresql.org/users-lounge/docs/faq.html</a></font><br/><font size="2">>> </font><code><fontsize="3"><br /><br /> _________________________________________________________________________<br /> Thise-mail and any attachments are confidential and may also be privileged and/or copyright <br /> material of Intec TelecomSystems PLC (or its affiliated companies). If you are not an <br /> intended or authorised recipient of this e-mailor have received it in error, please delete <br /> it immediately and notify the sender by e-mail. In such a case,reading, reproducing, <br /> printing or further dissemination of this e-mail is strictly prohibited and may be unlawful.<br /> Intec Telecom Systems PLC. does not represent or warrant that an attachment hereto is free <br /> from computerviruses or other defects. The opinions expressed in this e-mail and any <br /> attachments may be those of the authorand are not necessarily those of Intec Telecom <br /> Systems PLC. <br /><br /> This footnote also confirms that thisemail message has been swept by<br /> MIMEsweeper for the presence of computer viruses. <br /> __________________________________________________________________________<br/></font></code>
pgsql-hackers by date: