2 <title>Y2K Statement</title>
10 <ulink url="mailto:lockhart@alumni.caltech.edu">Thomas Lockhart</ulink>
15 The <productname>PostgreSQL</productname> Global Development Team provides
16 the <productname>Postgres</productname> software code tree as a public service,
17 without warranty and without liability for it's behavior or performance.
18 However, at the time of writing:
23 The author of this statement, a volunteer on the <productname>Postgres</productname>
24 support team since November, 1996, is not aware of
25 any problems in the <productname>Postgres</productname> code base related
26 to time transitions around Jan 1, 2000 (Y2K).
30 The author of this statement is not aware of any reports of Y2K problems
31 uncovered in regression testing
32 or in other field use of recent or current versions
33 of <productname>Postgres</productname>. We might have expected
34 to hear about problems if they existed, given the installed base and
35 the active participation of users on the support mailing lists.
39 To the best of the author's knowledge, the
40 assumptions Postgres makes about dates specified with a two-digit year
41 are documented in the current
42 <ulink url="http://www.postgresql.org/docs/user/datatype.htm">User's Guide</ulink>
43 in the chapter on data types.
44 For two-digit years, the significant transition year is 1970, not 2000;
45 i.e. <quote>70-01-01</quote> is interpreted as <quote>1970-01-01</quote>,
46 whereas <quote>69-01-01</quote> is interpreted as <quote>2069-01-01</quote>.
50 Any Y2K problems in the underlying OS related to obtaining "the
51 current time" may propagate into apparent Y2K problems in
52 <productname>Postgres</productname>.
58 <ulink url="http://www.gnu.org/software/year2000.html">The Gnu Project</ulink>
60 <ulink url="http://language.perl.com/news/y2k.html">The Perl Institute</ulink>
61 for further discussion of Y2K issues, particularly
62 as it relates to open source, no fee software.