Tom,
> The issue is not really what the raw timestamp value's range is.
> The issue is what range of dates do you have local timezone information
> for. Pay close attention to the difference here:
Ah, I see. I don't use timestamp with timezone much; I find the Unix
implementation of time zones inadequate for reality.
So, the answer is that TIMESTAMP WITH TIMEZONE is good through 2037, and
TIMESTAMP WITHOUT TIME ZONE is good through 10,000AD?
> PG is refusing to assign a time zone to the latter. The reason: our
> present code relies on the surrounding Unix system to provide timezone
> data, and it does so through Unix APIs that (on most boxen) overflow in
> 2038. Thus the above behavior.
And, on the up side, if the various *nixes fix their time zone behaviour past
2037, then Postgres will be automatically fixed as well, yes?
--
Josh Berkus
Aglio Database Solutions
San Francisco
