Skip site navigation (1) Skip section navigation (2)

Peripheral Links

Header And Logo

PostgreSQL
| The world's most advanced open source database.

Site Navigation

Search archives
  Advanced Search

Re: Year 2038 Bug?

  • From: "David E. Wheeler" <david(at)kineticode(dot)com>
  • To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
  • Cc: PostgreSQL-development Hackers <pgsql-hackers(at)postgresql(dot)org>
  • Subject: Re: Year 2038 Bug?
  • Date: Mon, 13 Oct 2008 11:19:27 -0700
  • Message-id: <F8DF8536-008A-45F7-8E7F-A2BF7A18F4EB@kineticode.com> <text/plain>
On Oct 13, 2008, at 11:13, Tom Lane wrote:


"David E. Wheeler" <david(at)kineticode(dot)com> writes:

Probably no problem, then. Do dates in PostgreSQL work for their
entire documented ranges on 32bit processors?


As long as the C compiler supports int64 ...


I was afraid you'd say that. See:

  http://code.google.com/p/y2038/wiki/WhyBother
Especially the "64 bit CPU doesn't mean 2038 clean" section. Again, maybe this doesn't apply to PostgreSQL; I'm just doing a bit of diligence. :-) 

Cheers,

David
Home | Main Index | Thread Index

Privacy Policy | About PostgreSQL
Copyright © 1996 – 2012 PostgreSQL Global Development Group