* Joe Conway (mail@joeconway.com) wrote:
> On 11/04/2015 01:24 PM, Alvaro Herrera wrote:
> > I agree with Pavel. Having a transaction timeout just does not make any
> > sense. I can see absolutely no use for it. An idle-in-transaction
> > timeout, on the other hand, is very useful.
>
> +1 -- agreed
I'm not sure of that. I can certainly see a use for transaction
timeouts- after all, they hold locks and can be very disruptive in the
long run. Further, there are cases where a transaction is normally very
fast and in a corner case it becomes extremely slow and disruptive to
the rest of the system. In those cases, having a timeout for it is
valuable.
David (adding him to the CC) actually developed a utility specifically
to identify what transactions are blocking what others and to kill off
other processes if they were running for too long and blocking higher
priority processes. It didn't matter, in that environment, if they were
idle-in-transaction or actively running.
David, please correct/confirm my recollection above.
Thanks!
Stephen