Re: [PATCH] lock_timeout and common SIGALRM framework

Boszormenyi Zoltan <zb@cybertec.at> writes:
>>> Try SET deadlock_timeout = 0;

Actually, when I try that I get

ERROR:  0 is outside the valid range for parameter "deadlock_timeout" (1 .. 2147483647)

So I don't see any bug here.  The places that are unconditionally doing
"enable_timeout_after(..., DeadlockTimeout);" are perfectly fine.  The
only place that might need an if-test has already got one:
         if (StatementTimeout > 0)
!             enable_timeout_after(STATEMENT_TIMEOUT, StatementTimeout);         else
!             disable_timeout(STATEMENT_TIMEOUT, false);

        regards, tom lane