Re: collector's time is wrong.(year 2038 problem)

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: 石原 和樹 <Kazuki(dot)Ishihara(at)keisetsu(dot)jp>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: collector's time is wrong.(year 2038 problem)
Date: 2016-11-02 14:35:04
Message-ID: 26502.1478097304@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

=?iso-2022-jp?B?GyRCQFA4NhsoQiAbJEJPQjx5GyhC?= <Kazuki(dot)Ishihara(at)keisetsu(dot)jp> writes:
> 1. Change current time. (e.g. Sep. 1st 2040)
> 2. Start PostgreSQL Service.

This is not going to work on any platform that uses 32-bit time_t.
It's not our bug, it's that the system time API doesn't work after 2038.

The short answer is that you're not going to still be using Windows 8
in 2040, so don't worry about it.

regards, tom lane

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Jamie Koceniak 2016-11-02 15:31:12 Re: BUG #14399: Order by id DESC causing bad query plan
Previous Message Tom Lane 2016-11-02 13:29:12 Re: Compilation of timezone source with zic fails (on mountpoint)