Re: BUG #4084: Some DST timezones switche to summer time (one week) later - Mailing list pgsql-bugs

From Zdenek Kotala
Subject Re: BUG #4084: Some DST timezones switche to summer time (one week) later
Date
Msg-id 47F4B23A.5080500@sun.com
Whole thread Raw
In response to BUG #4084: Some DST timezones switche to summer time (one week) later  ("Premysl Paska" <premek.paska@gmail.com>)
Responses Re: BUG #4084: Some DST timezones switche to summer time (one week) later
List pgsql-bugs
Premysl Paska napsal(a):
> The following bug has been logged online:
>
> Bug reference:      4084
> Logged by:          Premysl Paska
> Email address:      premek.paska@gmail.com
> PostgreSQL version: 8.0.15
> Operating system:   Linux
> Description:        Some DST timezones switche to summer time (one week)
> later
> Details:
>
> We use TIMESTAPM WITH TIMEZONE to insert datetime values into our DB. The
> problem is with the CEST timezone (Central European Summer Time; Prague) and
> possibly some others.
>
> The summer time started on 2008-03-30 02:00 in the CEST timezone shifting
> offset with respect to UTC from +1 to +2. But PostgreSQL kept inserting with
> the former +1 offset after this day. We tested it for various other dates
> and realized that it switches to the summer time one week later
> (2008-04-06).

Do you use system timezone for PostgreSQL or do you use postgres timezone file?
But anyway there was not any change in CET timezone for a long time.

> The same problem was reported with a North American  timezone.
>
> (BTW we have another problem with TZ, after we change TZ in the system, we
> must restart Postgres to apply it also to the DB.)

Yes, PostgreSQL caches TZ data, however any others application in system could
be confused too when you update TZ data as well.

        Zdenek

pgsql-bugs by date:

Previous
From: "jitendra"
Date:
Subject: BUG #4087: table creation problem using python
Next
From: ITAGAKI Takahiro
Date:
Subject: Re: BUG #4087: table creation problem using python