Re: [HACKERS] pgsql y2k bug? - Mailing list pgsql-hackers

From Bruce Momjian
Subject Re: [HACKERS] pgsql y2k bug?
Date
Msg-id 200001020210.VAA05416@candle.pha.pa.us
Whole thread Raw
In response to Re: [HACKERS] pgsql y2k bug?  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
> Bruce Momjian <pgman@candle.pha.pa.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@candle.pha.pa.us            |  (610)
853-3000+  If your life is a hard drive,     |  830 Blythe Avenue +  Christ can be your backup.        |  Drexel Hill,
Pennsylvania19026
 


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: [HACKERS] pgsql y2k bug?
Next
From: Tom Lane
Date:
Subject: Re: [BUGS] Date calc bug