| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "Trevor Talbot" <quension(at)gmail(dot)com> |
| Cc: | Magne Mæhre <Magne(dot)Mahre(at)sun(dot)com>, "Aidan Van Dyk" <aidan(at)highrise(dot)ca>, "Peter Eisentraut" <peter_e(at)gmx(dot)net>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Timezone database changes |
| Date: | 2007-10-11 13:47:56 |
| Message-ID: | 12334.1192110476@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
"Trevor Talbot" <quension(at)gmail(dot)com> writes:
> On 10/11/07, Magne M=E6hre <Magne(dot)Mahre(at)sun(dot)com> wrote:
>> Trevor Talbot wrote:
>>> That situation might sound a bit contrived, but I think the real point
>>> is that even for some records of observed times, the local time is the
>>> authoritative one, not UTC.
>>
>> ...and for that scenario you have TIMESTAMP WITHOUT TIME ZONE
> But that doesn't give you DST-sensitive display for free, which is
> tempting for application use, especially if the application is meant
> to be suitably generic.
If you are dealing only in local time, what do you need timezone for at
all?
Also note the possibility of coercing one type to the other on-the-fly
for display, or using the AT TIME ZONE construct.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Florian G. Pflug | 2007-10-11 13:57:15 | Re: full text search in 8.3 |
| Previous Message | Gregory Stark | 2007-10-11 13:42:47 | Re: [PATCHES] Eliminate more detoast copies for packed varlenas |