| From: | Pavel Borisov <pashkin(dot)elfe(at)gmail(dot)com> |
|---|---|
| To: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, 方徳輝 <javaeecoding(at)gmail(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Is postgres ready for 2038? |
| Date: | 2020-11-18 13:32:57 |
| Message-ID: | CALT9ZEFjjwyRt6VcSkbPBsMV1q2LjHRFEaqzXRsaOEcHa4HfqA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
>
> 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 <http://www.postgrespro.com>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bharath Rupireddy | 2020-11-18 13:39:48 | Re: [PATCH] postgres_fdw connection caching - cause remote sessions linger till the local session exit |
| Previous Message | Andrew Dunstan | 2020-11-18 12:56:54 | Re: Is postgres ready for 2038? |