| From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
|---|---|
| To: | Bruno Wolff III <bruno(at)wolff(dot)to> |
| Cc: | Dann Corbit <DCorbit(at)connx(dot)com>, Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, Greg Stark <gsstark(at)mit(dot)edu>, Tino Wildenhain <tino(at)wildenhain(dot)de>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>, "Marc G(dot) Fournier" <scrappy(at)postgresql(dot)org> |
| Subject: | Re: Imprecision of DAYS_PER_MONTH |
| Date: | 2005-07-22 19:55:37 |
| Message-ID: | 42E14F39.7030408@dunslane.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Bruno Wolff III wrote:
>On Fri, Jul 22, 2005 at 12:27:50 -0700,
> Dann Corbit <DCorbit(at)connx(dot)com> wrote:
>
>
>>Apparently, the Gregorian calendar has been fixed. From this:
>>http://www.physics.uq.edu.au/people/ross/phys2081/time/calendar.htm
>>
>>We have this:
>>"The Gregorian calendar has been modified since (before anything could
>>go wrong) to bring the Gregorian 365.2425 down to 365.2422 by cutting
>>out "leap centuries" that are divisible by 4000 thus giving an accuracy
>>of about one day in 20,000 years"
>>
>>
>
>That's interesting. So now we will have a year 4000 problem when there
>isn't a leap year as was previously scheduled.
>
>
>
>
remind me about that when we're a bit closer to the date.
cheers
andrew (who wasted a year of his life on y2k crap).
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2005-07-22 20:12:05 | Re: Checkpoint cost, looks like it is WAL/CRC |
| Previous Message | Bruno Wolff III | 2005-07-22 19:42:01 | Re: Imprecision of DAYS_PER_MONTH |