Skip site navigation (1) Skip section navigation (2)

Peripheral Links

Header And Logo

PostgreSQL
| The world's most advanced open source database.

Site Navigation

Search for
  Advanced Search

Re: BUG #3948: date/time functions returning wrong value


  • From: Magnus Hagander <magnus(at)hagander(dot)net>
  • To: Jorge Campins <jrcampins(at)cantv(dot)net>
  • Cc: pgsql-bugs(at)postgresql(dot)org
  • Subject: Re: BUG #3948: date/time functions returning wrong value
  • Date: Sun, 10 Feb 2008 00:47:53 +0100
  • Message-id: <47AE3BA9(dot)7090206(at)hagander(dot)net>

Jorge Campins wrote:
The following bug has been logged online:

Bug reference:      3948
Logged by:          Jorge Campins
Email address:      jrcampins(at)cantv(dot)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



Home | Main Index | Thread Index

Privacy Policy | PostgreSQL Archives hosted by Command Prompt, Inc. | Designed by tinysofa
Copyright © 1996 – 2008 PostgreSQL Global Development Group