Re: BUG #5466: Asia/Novosibirsk timezone problem

On Wed, May 19, 2010 at 3:12 PM, Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> wrote:
> Excerpts from Magnus Hagander's message of mié may 19 15:03:25 -0400 2010:
>> On Wed, May 19, 2010 at 3:00 PM, Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> wrote:
>> > Excerpts from Dmitry Funk's message of mié may 19 13:44:35 -0400 2010:
>
>> >> 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 = 'Asia/Novosibirsk'" in postgresql.conf
>> >>
>> >> Affected only Windows, not Linux.
>> >
>> > We have this in pgtz.c:
>> >
>> >    {
>> >        "N. Central Asia Standard Time", "N. Central Asia Daylight Time",
>> >        "Asia/Almaty"
>> >    },                          /* (GMT+06:00) 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.
>
> Well, ISTM it does make a difference, which is that there *is* DST info
> in the N. Central Asia Standard Time zone, no?  According the Dmitry,
> Almaty doesn't have DST, so it's wrong to report that zone.

Well, if we report it as Novosibirsk, it will have DST. Which users in
Almaty aren't supposed to have, so it'll be wrong for them. So it's
going to be wrong for one of them whichever way we go, won't it?

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