Josh Berkus <j...@agliodbs.com> writes:
> ls -l localtime
> lrwxrwxrwx 1 root root 31 2010-10-18 08:20 localtime ->
> /usr/share/zoneinfo/US/Mountain
> postgres=# select * from pg_settings where name = 'TimeZone';
> setting | Navajo
> There is actually a time zone "Navajo", which is a *separate* time zone
> from US/Mountain. Ideas on how this happened?
It's not all that separate: per the Olsen database,
Link America/Denver US/Mountain
Link America/Denver Navajo
Those are all aliases for the exact same timezone behavior, and PG
doesn't have any good way to choose which one you think is preferred.
It looks like it chooses the shortest name ... so in this case you'll
get Navajo. If you don't like that, set the timezone setting
explicitly or via the TZ environment variable for the postmaster.
regards, tom lane
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
