From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au> |
Cc: | josh(at)agliodbs(dot)com, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: timestamp with time zone a la sql99 |
Date: | 2004-10-26 01:52:00 |
Message-ID: | 3306.1098755520@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au> writes:
> That's worked for ages. What doesn't work is this:
> usatest=# select current_timestamp at time zone 'US/Arizona';
> ERROR: time zone "us/arizona" not recognized
Right, and similarly you can do
regression=# select '2004-10-25 21:32:33.430222 MST'::timestamptz;
timestamptz
-------------------------------
2004-10-26 00:32:33.430222-04
(1 row)
but not
regression=# select '2004-10-25 21:32:33.430222 US/Arizona'::timestamptz;
ERROR: invalid input syntax for type timestamp with time zone: "2004-10-25 21:32:33.430222 US/Arizona"
I would like to see both of these cases working in 8.1; and furthermore
I'd like to see the timezone specs coming back as entered, not as bare
numeric offsets. (This will need to be adjustable via a DateStyle
option, of course, but I want the information to be in there whether it
is displayed or not.)
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Tatsuo Ishii | 2004-10-26 03:44:49 | Re: Proposed Query Planner TODO items |
Previous Message | L.I. JUAN PATRICIO FLORES HERNANDEZ | 2004-10-26 01:45:41 | segment default |