| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Jeff Davis <pgsql(at)j-davis(dot)com> |
| Cc: | Christopher Browne <cbbrowne(at)gmail(dot)com>, Steve Crawford <scrawford(at)pinpointresearch(dot)com>, Alvaro Herrera <alvherre(at)commandprompt(dot)com>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: storing TZ along timestamps |
| Date: | 2011-06-03 00:28:57 |
| Message-ID: | BANLkTi=wsL84jF6MeaBctEP5397cNjOGGQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, Jun 2, 2011 at 3:02 PM, Jeff Davis <pgsql(at)j-davis(dot)com> wrote:
> On Thu, 2011-06-02 at 18:46 +0000, Christopher Browne wrote:
>> > 1. How would the time-zone be defined in this composite? Offset from GMT?
>> > Timezone (well, link thereto) with all DST rules intact? Would "extract"
>> > need to be modified to include the ability to grab the timezone?
>>
>> That doesn't seem appropriate, because timezones are not always
>> represented by strict offsets from GMT. Some frequently-used
>> timezones represent variable offsets. ("EDT/EST", I'm looking at
>> you!)
>
> In conjunction with a specific timestamp, a timezone does strictly map
> to a single offset.
But that doesn't seem like enough, because if someone adds '1 day',
knowing the offset isn't sufficient to figure out the answer. You
have to know where the DST boundary is.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Cédric Villemain | 2011-06-03 00:33:30 | Re: patch review : Add ability to constrain backend temporary file space |
| Previous Message | Noah Misch | 2011-06-03 00:25:21 | Re: Domains versus polymorphic functions, redux |