From: | Michael Fuhr <mike(at)fuhr(dot)org> |
---|---|
To: | "Giovanni M(dot)" <drayah(at)gmail(dot)com> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: PostgreSQL now() function returns incorrect time |
Date: | 2005-11-09 16:54:33 |
Message-ID: | 20051109165433.GA41463@winnie.fuhr.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Wed, Nov 09, 2005 at 02:24:28PM -0200, Giovanni M. wrote:
> I'm situated in Brazil and recently daylights savings/summer time kicked in
> and clocks were set one hour ahead. Now on my windows box the system clock
> automatically adjusted to the correct time. But performing the following
> query on the postgresql-8.0 server i get this result:
> select now()
> ----------------------
> 2005-11-09 13:22:27.625-03
> while the actual current time is 14:22h, and being reported correctly in
> the windows system clock
> I have tried finding some information in the documentation and came across
> locale settings in the postgresql.conf configuration file but Im not sure if
> this is the correct place to be looking. Should i set the timezone property
> in postgresql.conf to something other than unknown?
Do you see the correct time if you do the following?
SET timezone TO 'Brazil/East';
SELECT now();
If so then change the timezone line in postgresql.conf to:
timezone = Brazil/East
Then reload or restart the database.
--
Michael Fuhr
From | Date | Subject | |
---|---|---|---|
Next Message | Brian Mathis | 2005-11-09 17:33:04 | libpq version in rpm packages |
Previous Message | Markus Wollny | 2005-11-09 16:30:57 | invalid UTF-8 byte sequence detected |