Re: Is postgres ready for 2038?
От
Pavel Borisov
Тема
Re: Is postgres ready for 2038?
Дата
Msg-id
CALT9ZEGrHdzymFPrezRMmOpEHq6VWt3bSrTF9uB9rpCqiNqq1A@mail.gmail.com
Ответ на
Список
Дерево обсуждения
Is postgres ready for 2038? 方徳輝 <javaeecoding@gmail.com>
Re: Is postgres ready for 2038? Tom Lane <tgl@sss.pgh.pa.us>
Re: Is postgres ready for 2038? Andrew Dunstan <andrew@dunslane.net>
Re: Is postgres ready for 2038? Pavel Borisov <pashkin.elfe@gmail.com>
Re: Is postgres ready for 2038? Tom Lane <tgl@sss.pgh.pa.us>
Re: Is postgres ready for 2038? Andrew Dunstan <andrew@dunslane.net>
Re: Is postgres ready for 2038? Tom Lane <tgl@sss.pgh.pa.us>
Re: Is postgres ready for 2038? Greg Stark <stark@mit.edu>
Re: Is postgres ready for 2038? Pavel Borisov <pashkin.elfe@gmail.com>
Re: Is postgres ready for 2038? Tom Lane <tgl@sss.pgh.pa.us>
Re: Is postgres ready for 2038? 方徳輝 <javaeecoding@gmail.com>
Re: Is postgres ready for 2038? Pavel Borisov <pashkin.elfe@gmail.com>
Re: Is postgres ready for 2038? Pavel Borisov <pashkin.elfe@gmail.com>
There are no 32bit Windows version builds since Postgres 11, see:
https://www.postgresql.org/download/windows/
but Postgres 13 still has the same 2038 problems.
As @Pavel Borisov hints , I can find `_USE_32BIT_TIME_T` code here:
https://github.com/postgres/postgres/search?q=_USE_32BIT_TIME_T
Is it a good idea to remove `_USE_32BIT_TIME_T` code and build with 64bit Perl
might solve 2038 problem?
As it was mentioned above `_USE_32BIT_TIME_T` is not default flag for msvc builds, but perl can set this on purpose (or on the reason it is very ancient). Postgres will not set `_USE_32BIT_TIME_T` itself and and by default compiles with 64bit time, which is correct. But it regards the perl's choice in case it is made on purpose. If you face the problem with PG compiled with non-2038 compatible time please first check your perl, this is the reason.
Regards, Pavel Borisov.
В списке pgsql-hackers по дате отправления
От: Alexander Korotkov
Дата:
От: Bharath Rupireddy
Дата:
