Re: possible time change issue - known problem?

On 7 Apr 2003 at 10:50, Tom Lane wrote:

> "Dan Langille" <dan(at)langille(dot)org> writes:
> > On 7 Apr 2003 at 10:32, Tom Lane wrote:
> >> Type INTERVAL knows about months and seconds, nothing else.
>
> > Hmmm, months and seconds only. Then is the documentation wrong?
>
> No, the docs are right, but the physical storage is months and seconds.
> For instance, '1 year' becomes '12 months' (okay) and '1 week' becomes
> '604800 seconds' (not so okay). Adding 'day' as a basic element would
> allow correct handling of cross-DST-boundary cases.

Ahhhh, OK, I understand.

> >> I've opined in the past that it should be months, days, and seconds,
> >> but no one seems excited enough about the issue to do the nontrivial
> >> work involved ...
>
> > If it truly is that trivial, please point me at the file I need to
> > hack.
>
> Didn't I just say that I think it's *not* trivial? But anyway, the
> interval-related functions are in some subset of

*cough* yes, sorry, I misunderstood. So much for my spending the
rest of today fixing it...
--
Dan Langille : http://www.langille.org/