Re: [ADMIN] Date Return must be As per Natural Calander - Mailing list pgsql-bugs

From Tom Lane
Subject Re: [ADMIN] Date Return must be As per Natural Calander
Date
Msg-id 7495.1046145998@sss.pgh.pa.us
Whole thread Raw
In response to Re: [ADMIN] Date Return must be As per Natural Calander  (Robert Treat <xzilla@users.sourceforge.net>)
Responses Re: [ADMIN] Date Return must be As per Natural Calander  ("Ross J. Reedstrom" <reedstrm@rice.edu>)
List pgsql-bugs
Robert Treat <xzilla@users.sourceforge.net> writes:
> I guess adding 1 day to 1752-09-02 should give us 1752-09-14, but your
> right, it gives us 1752-09-03.

As was pointed out at length just recently, the transition from Julian
to Gregorian calendars happened at different times in different places.
So the above claim is only correct for some places.

The conclusion from the previous discussion was that our existing
behavior (extrapolate Gregorian rules backwards indefinitely) is as
defensible as anything else that would be likely to get coded.

I suppose you could imagine something that looks at the locale and
tries to guess the appropriate transition date ... but I don't foresee
anyone getting very excited about coding it.

            regards, tom lane

pgsql-bugs by date:

Previous
From: pgsql-bugs@postgresql.org
Date:
Subject: Bug #903: Performance Hangs during Lookups
Next
From: Tom Lane
Date:
Subject: Re: Bug #903: Performance Hangs during Lookups