Re: [PATCH] lock_timeout and common SIGALRM framework

Excerpts from Tom Lane's message of vie jul 13 18:23:31 -0400 2012:
>
> 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.

I committed this patch without changing this.  If this needs patched,
please speak up.  I also considered adding a comment on
enable_timeout_after about calling it with a delay of 0, but refrained;
if anybody thinks it's necessary, suggestions are welcome.

--
Álvaro Herrera <alvherre@commandprompt.com>
The PostgreSQL Company - Command Prompt, Inc.
PostgreSQL Replication, Consulting, Custom Development, 24x7 support