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

From Andrew Dunstan
Subject Re: Is postgres ready for 2038?
Date
Msg-id 004d74c6-0959-4b29-178a-5edfe56c4081@dunslane.net
Whole thread Raw
In response to Re: Is postgres ready for 2038?  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Is postgres ready for 2038?  (Pavel Borisov <pashkin.elfe@gmail.com>)
List pgsql-hackers
On 11/17/20 11:04 AM, Tom Lane wrote:
> =?UTF-8?B?5pa55b6z6Lyd?= <javaeecoding@gmail.com> writes:
>> Is there any road map for 2038 problems in Postgres?
> Postgres has no problem with post-2038 dates as long as you are using a
> system with 64-bit time_t.  In other words, the road map is "get off
> Windows, or press Microsoft to fix their problems".
>
>         


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.


cheers


andrew


--
Andrew Dunstan
EDB: https://www.enterprisedb.com




pgsql-hackers by date:

Previous
From: Magnus Hagander
Date:
Subject: Re: Devel docs on website reloading
Next
From: Pavel Borisov
Date:
Subject: Re: Is postgres ready for 2038?