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

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

From: "Jonathan Brinkman" <JB(at)BlackSkyTech(dot)com>
To: "'Robert Haas'" <robertmhaas(at)gmail(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-22 12:56:47
Message-ID: 003201cbe890$9c763bc0$d562b340$@com (view raw or whole thread)
Lists: pgsql-bugs
ALTER ROLE postgres SET time zone 'America/New_York';
Fixed the problem!

I applied this to my dev server DB anyways, so maybe this will be fixed the
next time I migrate to Production.
ALTER DATABASE beta_cms_main SET time zone 'America/New_York';

-----Original Message-----
From: Robert Haas [mailto:robertmhaas(at)gmail(dot)com] 
Sent: Monday, March 21, 2011 11:50 AM
To: JB(at)blackskytech(dot)com
Cc: Tom Lane; Kevin Grittner; pgsql-bugs(at)postgresql(dot)org
Subject: Re: [BUGS] TO_CHAR(timestamptz,datetimeformat) wrong after DST

On Mon, Mar 21, 2011 at 9:13 AM, Jonathan Brinkman <JB(at)blackskytech(dot)com>
> 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
The Enterprise PostgreSQL Company

In response to

pgsql-bugs by date

Next:From: Alvaro HerreraDate: 2011-03-22 14:51:38
Subject: Re: BUG #5937: initdb: FATAL error: could not open relation with OID 2608
Previous:From: AdriaanDate: 2011-03-22 09:50:29
Subject: BUG #5940: Creating a foreign key on an empty table locks table

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