Re: Timezones -- what comes out does not go in?

From: Alvaro Herrera <alvherre(at)commandprompt(dot)com>
To: Julian Scarfe <julian(at)avbrief(dot)com>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: Timezones -- what comes out does not go in?
Date: 2006-08-16 14:22:13
Message-ID: 20060816142213.GA27322@alvh.no-ip.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Julian Scarfe wrote:
> The timezone on our boxes is set to Etc/UCT (possibly a distro default).
>
> (psql 8.1.4)
>
> => select to_char(current_timestamp, 'HH24:MI:SS TZ');
> to_char
> --------------
> 09:05:48 UCT
> (1 row)
>
> => select '09:05:48 UCT'::time;
> ERROR: invalid input syntax for type time: "09:05:48 UCT"
>
> Is this behaviour expected? Desirable?

It is expected, because back in 8.1 the timezones recognized came from a
hardcoded table. It's not desirable of course. But on the other hand,
it's fixed in the development code:

alvherre=# set timezone to 'Etc/UCT';
SET
alvherre=# select to_char(current_timestamp, 'HH24:MI:SS TZ');
to_char
--------------
14:19:05 UCT
(1 fila)

alvherre=# select '14:19:05 UCT'::time;
time
----------
14:19:05
(1 fila)

--
Alvaro Herrera http://www.CommandPrompt.com/
PostgreSQL Replication, Consulting, Custom Development, 24x7 support

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Tom Lane 2006-08-16 14:23:01 Re: Massive slowdown when LIMIT applied
Previous Message Tom Lane 2006-08-16 14:19:25 Re: Timezones -- what comes out does not go in?