When selecting with the AT TIME ZONE or timezone function, the returned value
is not always a timestamp. This is inconsistent with the documentation.
To reproduce this problem, run these two queries.
SELECT now() AT TIME ZONE 'EST'
returns 2003-03-13 21:27:14.63401-05
SELECT now() AT TIME ZON
A kind person on the pgsql-general list told me.
"This appears to be a simple typo in the pg_proc entry for the function.
The underlying C code thinks it is returning a timestamp without time
zone, but that's not what the pg_proc entry has.
You can fix this in an existing database by doing
UPDAT
In addition, I have upgraded to postgre 7.3.2 instead of postgre 7.3 and I get
the exact same output except that years are included in the interval.
It still returns an interval instead of a timestamp.
josh.
On March 13, 2003 10:12 pm, Joshua Moore-Oliva wrote:
> When selecting with the AT TI
When selecting with the AT TIME ZONE or timezone function, the returned value
is not always a timestamp. This is inconsistent with the documentation.
To reproduce this problem, run these two queries.
SELECT now() AT TIME ZONE 'EST'
returns 2003-03-13 21:27:14.63401-05
SELECT now() AT TIME ZONE
