Re: lock_timeout GUC patch

<p>we already have statement timeout it seems the natural easy to implement this is with more hairy logic to calculate
thetimeout until the next of the three timeouts should fire and set sigalarm. I sympathize with whoever tries to work
thatthrough though, the logic is hairy enough with just the two variables...but at least we know that sigalarm works or
atleast it had better...<p>greg<p><blockquote type="cite">On 20 Jan 2010 00:27, "Robert Haas" <<a
href="mailto:robertmhaas@gmail.com">robertmhaas@gmail.com</a>>wrote:<br /><br /><p><font color="#500050">On Tue, Jan
19,2010 at 7:10 PM, Tom Lane <<a href="mailto:tgl@sss.pgh.pa.us">tgl@sss.pgh.pa.us</a>> wrote: > Robert Haas
<robertmhaas@gmai...</font>Thatseems reasonable to me.  I'd like to have the functionality, but<br /> pushing it off
arelease sounds reasonable, if we're worried that it<br /> will be destabilizing.<br /><font color="#888888"><br />
...Robert<br/></font><p><font color="#500050"> -- Sent via pgsql-hackers mailing list (<a
href="mailto:pgsql-hackers@postgresql.org">pgsql-hackers@postgresql.org</a>)To make changes to your
subs...</font></blockquote>