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

Re: TO_CHAR(timestamptz,datetimeformat) wrong after DST change

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: JB(at)blackskytech(dot)com
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Kevin Grittner <Kevin(dot)Grittner(at)wicourts(dot)gov>, pgsql-bugs(at)postgresql(dot)org
Subject: Re: TO_CHAR(timestamptz,datetimeformat) wrong after DST change
Date: 2011-03-21 15:49:42
Message-ID: AANLkTi=ab67C4rC4E0NUHwhvt_KPetqDti7YSHP4_OvU@mail.gmail.com (view raw or flat)
Thread:
Lists: pgsql-bugs
On Mon, Mar 21, 2011 at 9:13 AM, Jonathan Brinkman <JB(at)blackskytech(dot)com> wrote:
> I understand now that I must use America/New_York for DST to function.  I
> see in select * from pg_timezone_names ; that 'EDT' is a shortcut. I tried
> to SET TIME ZONE 'EDT'; but PG doesn't seem to like that.
>
> My problem is that the corrected time zone (America/New_York) doesn't seem
> to stick after updating. I update it in psql (cmd line) and within psql it
> returns correctly. But when I then view now() from command line the DST
> change is not there and time zone is again 'EST'. So:

SET is a session-local command.  You may want to update it in
postgresql.conf (and then reload the config using pg_ctl reload).  Or
you could use ALTER ROLE .. SET or ALTER DATABASE .. SET, if you don't
want to change it globally.

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

In response to

Responses

pgsql-bugs by date

Next:From: Bernd HelmleDate: 2011-03-21 16:44:41
Subject: Warm Standby startup process unconditionally hangs
Previous:From: Etienne RobillardDate: 2011-03-21 15:29:01
Subject: Re: BUG #5937: initdb: FATAL error: could not open relation with OID 2608

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group