Re: 32 bit libpq fail to connecting when set a very large "connect_timeout" value

From: John R Pierce <pierce(at)hogranch(dot)com>
To: pgsql-bugs(at)postgresql(dot)org
Subject: Re: 32 bit libpq fail to connecting when set a very large "connect_timeout" value
Date: 2014-10-21 18:02:11
Message-ID: 54469FA3.2050200@hogranch.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On 10/21/2014 10:49 AM, Tom Lane wrote:
> On my Linux box, it looks like time_t is defined as "long int", which
> means problem solved on 64-bit machines. If anyone is still using
> 32-bit hardware in 2038, they're probably going to have to endure an
> ABI break to widen time_t to int64.

FWIW, on a 32bit CentOS 5 (kernel 2.6.18.el5) box I still have around,
it looks like time_t is __TIME_T_TYPE which is __SLONGWORD_TYPE which is
long int

(per grepping .h stuff in /usr/include...)

$ uname -a
Linux *** 2.6.18-398.el5 #1 SMP Tue Sep 16 20:51:48 EDT 2014 i686 i686
i386 GNU/Linux

--
john r pierce 37N 122W
somewhere on the middle of the left coast

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Peter Bailis 2014-10-21 18:18:28 Re: BUG #11732: Non-serializable outcomes under serializable isolation
Previous Message Tom Lane 2014-10-21 17:55:33 Re: BUG #11734: The "<<=" operator on "inet" values does not return the expected result.