Re: The timezone oddities

From: Rob Sargent <robjsargent(at)gmail(dot)com>
To:
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: The timezone oddities
Date: 2014-02-04 22:48:50
Message-ID: 52F16E52.6070400@gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On 02/04/2014 03:44 PM, Tom Lane wrote:
> Adrian Klaver <adrian(dot)klaver(at)gmail(dot)com> writes:
>> On 02/04/2014 12:31 PM, Rob Sargent wrote:
>>> Perhaps building from source does make a guess at TZ. I am not residing
>>> in the Navaho national territory, but is that just Mountain time?
>> Yes:
>> http://en.wikipedia.org/wiki/List_of_tz_database_time_zones
>> The reason for specificity is that the Navajo Nation observes DST, while
>> the rest of Arizona does not.
> Not quite. The zoneinfo database has a number of names for Mountain Time
> with DST, eg America/Denver. A quick look says that "Navajo" is just an
> alias for that one, so no probe of the system's timezone behavior is going
> to be able to tell the difference. IIRC, given two zone names that both
> match the system's behavior equally well, initdb chooses the shorter one.
> That heuristic produces good results in many places, but not so much here.
>
> Note that this is exactly the same choice of zone you'd have gotten from
> pre-9.2 if it wasn't told a timezone setting to use. We only moved this
> examination of the system's behavior from every-postmaster-start to
> initdb.
>
> regards, tom lane
Interesting. I'm cool with it being 'Navaho' as that has a certain
nostalgic resonance with me.

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Andrew Sullivan 2014-02-05 01:36:52 Re: Re: Drop all overloads of a function without knowing parameter types
Previous Message Tom Lane 2014-02-04 22:44:38 Re: The timezone oddities