| From: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> |
|---|---|
| To: | Dmitry Funk <diffor(at)gmail(dot)com> |
| Cc: | pgsql-bugs <pgsql-bugs(at)postgresql(dot)org>, Magnus Hagander <magnus(at)hagander(dot)net> |
| Subject: | Re: BUG #5466: Asia/Novosibirsk timezone problem |
| Date: | 2010-05-19 19:00:35 |
| Message-ID: | 1274295519-sup-665@alvh.no-ip.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
Excerpts from Dmitry Funk's message of mié may 19 13:44:35 -0400 2010:
> Description: Asia/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 = '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.
--
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Magnus Hagander | 2010-05-19 19:03:25 | Re: BUG #5466: Asia/Novosibirsk timezone problem |
| Previous Message | Joseph Conway | 2010-05-19 18:41:41 | Re: BUG #5465: dblink TCP connection hangs blocking translation from being terminated |