Postgres Pro
Downloads
Home   >   mailing lists

Re: Is postgres ready for 2038? - Mailing list pgsql-hackers

From Pavel Borisov
Subject Re: Is postgres ready for 2038?
Date
Msg-id CALT9ZEFjjwyRt6VcSkbPBsMV1q2LjHRFEaqzXRsaOEcHa4HfqA@mail.gmail.com
Whole thread Raw
In response to Re: Is postgres ready for 2038?  (Andrew Dunstan <andrew@dunslane.net>)
Responses Re: Is postgres ready for 2038?  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
Tree view
But it does: "time_t is, by default, equivalent to __time64_t." See

<https://docs.microsoft.com/en-us/cpp/c-runtime-library/reference/time-time32-time64?view=msvc-160>


Maybe we need to dig a little more to see what's going on here.

How about just a mention in the future documentation to never ever define _USE_32BIT_TIME_T when compiling PG under Windows? Should be enough, I suppose.

--
Best regards,
Pavel Borisov

Postgres Professional: http://postgrespro.com

pgsql-hackers by date:

Previous
From: Andrew Dunstan
Date:
Subject: Re: Is postgres ready for 2038?
Next
From: Bharath Rupireddy
Date:
Subject: Re: [PATCH] postgres_fdw connection caching - cause remote sessions linger till the local session exit