Skip site navigation (1)
Skip section navigation (2)
Peripheral Links
Header And Logo
|
Site Navigation
Year 2038 Bug?
- From: "David E. Wheeler" <david(at)kineticode(dot)com>
- To: PostgreSQL-development Hackers <pgsql-hackers(at)postgresql(dot)org>
- Subject: Year 2038 Bug?
- Date: Mon, 13 Oct 2008 10:52:36 -0700
- Message-id: <4D65801C-C71F-46C6-9AE9-BB60A35C8A0F@kineticode.com> <text/plain>
Howdy,Not sure if PostgreSQL uses time_t, but if so, this project provides useful code (a drop-in replacement for time.h) to address the 2038 bug on 32-bit platforms.
http://code.google.com/p/y2038/ Useful for PostgreSQL? Best, David
- Follow-Ups:
- Re: Year 2038 Bug?
- From: Tom Lane
- Re: Year 2038 Bug?
- Prev by Date: Re: A small note about the difficulty of managing subprojects
- Next by Date: Re: Year 2038 Bug?
- Previous by thread: out-of-date comment in auto-generated oidjoins.sql
- Next by thread: Re: Year 2038 Bug?
- Indexes: