Re: timestamp with time zone a la sql99

From: Bruno Wolff III <bruno(at)wolff(dot)to>
To: Dennis Bjorklund <db(at)zigo(dot)dhs(dot)org>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Robert Treat <xzilla(at)users(dot)sourceforge(dot)net>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: timestamp with time zone a la sql99
Date: 2004-10-22 14:56:44
Message-ID: 20041022145644.GA17238@wolff.to
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Fri, Oct 22, 2004 at 16:28:12 +0200,
Dennis Bjorklund <db(at)zigo(dot)dhs(dot)org> wrote:
> On Fri, 22 Oct 2004, Tom Lane wrote:
>
> > As far as I can tell, Dennis is planning slavish adherence to the spec,
> > which will mean that the datatype is unable to cope effectively with
> > daylight-savings issues. So I'm unconvinced that it will be very
> > helpful to you for remembering local time in addition to true
> > (universal) time.
>
> And exactly what issues is it that you see? The only thing I can think of
> is if you have a timestamp and then add an interval to it so we jump past
> the daylight saving time change date. Then the new timestamp will keep the
> old timezone data of say +01 even though we now have jumped into the
> daylight saving period of +02.

I think for just storing values you are fine. When it comes to adding or
subtracting intervals you might get some unexpected results.

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Agent M 2004-10-22 15:06:12 "UNICODE" encoding
Previous Message Tom Lane 2004-10-22 14:54:19 Re: timestamp with time zone a la sql99