Re: Is postgres ready for 2038?

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.