On Sun, Nov 27, 2005 at 11:27:54AM -0700, Michael Fuhr wrote: > On Sun, Nov 27, 2005 at 08:45:18AM -0700, Michael Fuhr wrote: > > Looks like the value is stuck at 2^31 - 1 seconds: > > I see this behavior back to at least 7.3. I'd guess it's because > strtol() indicates overflow by returning LONG_MAX and setting errno > to ERANGE, but the code doesn't check for that.
Is this worth looking at for the upcoming dot releases? It's apparently a longstanding behavior that almost nobody encounters, yet knowingly not addressing it seems a bit MySQLish ;-) Here's the start of the thread for anybody who missed it: http://archives.postgresql.org/pgsql-hackers/2005-11/msg01385.php -- Michael Fuhr ---------------------------(end of broadcast)--------------------------- TIP 2: Don't 'kill -9' the postmaster
