| From: | "David E(dot) Wheeler" <david(at)kineticode(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | David Fetter <david(at)fetter(dot)org>, Kevin Grittner <Kevin(dot)Grittner(at)wicourts(dot)gov>, PG Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Timestamp to time_t |
| Date: | 2009-09-15 17:30:15 |
| Message-ID: | 1CB5F258-6423-46A8-AC1C-FB264F565F82@kineticode.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Sep 15, 2009, at 10:17 AM, Tom Lane wrote:
>> try=# select extract(timezone_hour from '2001-02-16 20:38:40 America/
>> Los_Angeles'::timestamptz);
>
> You appear to be confusing what PG currently does with what the spec
> says.
Sorry, I thought you were referring to what PostgreSQL does. Would I
be wrong in thinking that the current behavior might be surprising to
some? I mean, I'd really like a timestamptz that tracked the tz or
offset that was used to create its value…
I'm sure that's been on the ToDo list for time immemorial.
Best,
David
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2009-09-15 17:48:07 | Re: WIP: generalized index constraints |
| Previous Message | Jeff Davis | 2009-09-15 17:28:28 | Re: WIP: generalized index constraints |