Re: BUG #5466: Asia/Novosibirsk timezone problem

On Wed, May 19, 2010 at 3:00 PM, Alvaro Herrera <alvherre@alvh.no-ip.org> w=
rote:
> Excerpts from Dmitry Funk's message of mi=E9 may 19 13:44:35 -0400 2010:
>
>> Description: =A0 =A0 =A0 =A0Asia/Novosibirsk timezone problem
>> Details:
>>
>> Current system timezone: Asia/Novosibisk
>>
>> PostgreSQL on query "show timezone" show answer "Asia/Almaty"
>>
>> Asia/Novosibisk has daylight saving time
>> Asia/Almaty NOT has daylight saving time
>> and result of now() is wrong
>>
>> Workaround: "timezone =3D 'Asia/Novosibirsk'" in postgresql.conf
>>
>> Affected only Windows, not Linux.
>
> We have this in pgtz.c:
>
> =A0 =A0{
> =A0 =A0 =A0 =A0"N. Central Asia Standard Time", "N. Central Asia Daylight=
 Time",
> =A0 =A0 =A0 =A0"Asia/Almaty"
> =A0 =A0}, =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0/* (GMT+06:0=
0) Almaty, Novosibirsk */
>
> Which is probably wrong.

Why? :-)

Windows makes no difference between Almaty and Novosibirsk in it's
listing. If we pick the Novosibirsk one by default, that will just
break Almaty. There's no real easy way for us to find the difference
between those, since we're just matching on those two strings.

--=20
 Magnus Hagander
 Me: http://www.hagander.net/
 Work: http://www.redpill-linpro.com/