Re: [HACKERS] pgsql y2k bug?

From: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Ed Loehr <eloehr(at)austin(dot)rr(dot)com>, pghackers <pgsql-hackers(at)postgreSQL(dot)org>
Subject: Re: [HACKERS] pgsql y2k bug?
Date: 2000-01-02 02:10:32
Message-ID: 200001020210.VAA05416@candle.pha.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> writes:
> > I am attaching a diff to fix the problem. We were reporting only a
> > 2-digit year, and tm_year reports years since 1900, so it was reporting
> > 100 for year 2000. The field was %02d, but the number was three digits
> > so it printed all three.
>
> If you are going to go to 4-digit years in timestamps, I think you also
> need to increase the TIMESTAMP_SIZE constant used by elog.c when
> ELOG_TIMESTAMPS is set.
>
> An alternative solution is to print time->tm_year % 100.
>
> Either of these solutions might break existing programs that analyze
> logfiles, if any there be...

Done. Length increased by 2 from 28 to 30.

--
Bruce Momjian | http://www.op.net/~candle
maillist(at)candle(dot)pha(dot)pa(dot)us | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Don Baccus 2000-01-02 03:09:38 Re: [HACKERS] dubious improvement in new psql
Previous Message Tom Lane 2000-01-02 02:06:22 Re: [HACKERS] pgsql y2k bug?