From: | Magnus Hagander <magnus(at)hagander(dot)net> |
---|---|
To: | Diffor <diffor(at)gmail(dot)com> |
Cc: | pgsql-bugs <pgsql-bugs(at)postgresql(dot)org> |
Subject: | Re: BUG #5466: Asia/Novosibirsk timezone problem |
Date: | 2010-05-20 14:13:08 |
Message-ID: | AANLkTineX4Tvq0r0YQbIIKCb64jm33uANdnKfm7mErxR@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
Ah, good reference - thanks for digging that up. Interstingly enough
they seem to have just removed Almaty - and not put it anywhere else
:-)
But as someone said, they're being screwed, but only by MS, not us.
I've applied the change to pgtz.c. It will be in the next releases.
//Magnus
On Thu, May 20, 2010 at 3:54 AM, Diffor <diffor(at)gmail(dot)com> wrote:
> December 2009 cumulative time zone update for Microsoft Windows operating systems:
> http://support.microsoft.com/?kbid=976098
>
> pgtz.c is outdated:
>>N. Central Asia Standard Time:
>>Removes “Almaty” from the “(GMT+06:00) Almaty, Novosibirsk” time zone.
>
--
Magnus Hagander
Me: http://www.hagander.net/
Work: http://www.redpill-linpro.com/
From | Date | Subject | |
---|---|---|---|
Next Message | KOIZUMI Satoru | 2010-05-20 16:57:59 | BUG #5467: wrong classification at index |
Previous Message | Krzysztof Nienartowicz | 2010-05-20 14:00:03 | Query causing explosion of temp space with join involving partitioning |