Re: lock_timeout GUC patch

we already have statement timeout it seems the natural easy to implement
this is with more hairy logic to calculate the timeout until the next of the
three timeouts should fire and set sigalarm. I sympathize with whoever tries
to work that through though, the logic is hairy enough with just the two
variables...but at least we know that sigalarm works or at least it had
better...

greg

On 20 Jan 2010 00:27, "Robert Haas" <robertmhaas(at)gmail(dot)com> wrote:

On Tue, Jan 19, 2010 at 7:10 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote: >
Robert Haas <robertmhaas(at)gmai(dot)(dot)(dot)
That seems reasonable to me. I'd like to have the functionality, but
pushing it off a release sounds reasonable, if we're worried that it
will be destabilizing.

...Robert

-- Sent via pgsql-hackers mailing list (pgsql-hackers(at)postgresql(dot)org) To
make changes to your subs...