Re: timestamp bug

Ouch. Ok, that looks like it. I guess I should just set the time part to
13:00 (when DST never changes)? Or, can I set the time zone to GMT (for
this single SQL statement) or something that doesn't have DST? Perhaps a
different data type? Suggestions?

Thanks,
-Cedar

On Sun, 20 May 2001, Richard Huxton wrote:

> Cedar Cox wrote:
> >
> > There appears to be a bug in timestamp/interval addition. It happens in
> > both PG version 7.0.2 and 7.1. There is a duplicate day (2001 Sep 07) and
> > a missing day (2002 Apr 04). I discovered this by accident when I asked
> > the interface I'm writing for a 365 day long calendar.. Interestingly,
> > the missing day thing (second example) doesn't happen if only adding a few
> > days (like the first example). I didn't go into detail to find the point
> > at which it does happen.
>
> you're not hitting an issue with clocks going forward/back for
> summertime/daylight savings time?
>
> - Richard Huxton
>