Re: BUG #3948: date/time functions returning wrong value - Mailing list pgsql-bugs

From Magnus Hagander
Subject Re: BUG #3948: date/time functions returning wrong value
Date
Msg-id 47AE3BA9.7090206@hagander.net
Whole thread Raw
In response to BUG #3948: date/time functions returning wrong value  ("Jorge Campins" <jrcampins@cantv.net>)
Responses Re: BUG #3948: date/time functions returning wrong value  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-bugs
Jorge Campins wrote:
> The following bug has been logged online:
>
> Bug reference:      3948
> Logged by:          Jorge Campins
> Email address:      jrcampins@cantv.net
> PostgreSQL version: 8.1
> Operating system:   Windows XP
> Description:        date/time functions returning wrong value
> Details:
>
> As you might be aware, recently Venezuela has changed his timezone from GMT
> -4 to GMT -4:30. Windows implemented a new timezone for us, "Caracas", to be
> used instead of "Caracas/La Paz".
>
> As soon as I changed my computer's timezone to "Caracas", PostgreSQL
> date/time functions such as current_timestamp and localtimestamp started to
> return a wrong value (I guess they don't recognize the new timezone so they
> are returning GMT).
>
> Then I change it to "La Paz", and once again they returned my computer's
> time, but of course it has half an hour difference.
>
> I realize this is not really a bug. We will really appreciate your effort to
> solve this problem at your earliest convenience.

Try setting your timezone in postgresql.conf - that should override
whatever Windows has for you.

//Magnus

pgsql-bugs by date:

Previous
From: "Jorge Campins"
Date:
Subject: BUG #3948: date/time functions returning wrong value
Next
From: Tom Lane
Date:
Subject: Re: BUG #3948: date/time functions returning wrong value