Re: Date with time zone

From: Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Eduardo Piombino <drakorg(at)gmail(dot)com>, pgsql-general(at)postgresql(dot)org, Adrian Klaver <aklaver(at)comcast(dot)net>
Subject: Re: Date with time zone
Date: 2009-11-29 05:06:20
Message-ID: dcc563d10911282106q64717e96j45261621dd3044fd@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Sat, Nov 28, 2009 at 4:57 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Eduardo Piombino <drakorg(at)gmail(dot)com> writes:
>> I see current criteria and all the SQL-standard compliance policy, but
>> wouldn't it still make sense to be able to store a date reference, along
>> with a time zone reference?
>> Wouldn't it be useful, wouldn't it be elegant?
>
> It seems pretty ill-defined to me, considering that many jurisdictions
> don't switch daylight savings time at local midnight.  How would you
> know which zone applied on a DST transition date?

Yeah, I think the only reasonable way to define a date with a timezone
would be as some kind of interval, starting at 00:00:00 and going
until 23:59:59.99999 (or < 00:00:00 next day, whichever is more
accurate. On spring forward / fall back days it would be 23 or 25
hours respectively. I'm not sure what you'd DO with it though.

> TIME WITH TIME ZONE.  We only put it in for minimal spec compliance.

Yeah, it's kinda twilight zonish to me.

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Tech 2010 2009-11-29 06:02:21 Re: vacuumdb: vacuuming of database "xy" failed: PANIC: corrupted item pointer: 19227
Previous Message Robert Hartung 2009-11-29 03:04:02 8.45.1 on mac - Plist problems