Received: from maia.hub.org (maia-5.hub.org [200.46.204.29]) by mail.postgresql.org (Postfix) with ESMTP id 42ED21337BC3 for ; Tue, 15 Mar 2011 16:50:49 -0300 (ADT) Received: from mail.postgresql.org ([200.46.204.86]) by maia.hub.org (mx1.hub.org [200.46.204.29]) (amavisd-maia, port 10024) with ESMTP id 92240-06 for ; Tue, 15 Mar 2011 19:50:39 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by mail.postgresql.org (Postfix) with ESMTP id 7B0F71337BEA for ; Tue, 15 Mar 2011 16:50:38 -0300 (ADT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.2/8.14.2) with ESMTP id p2FJoYae003504; Tue, 15 Mar 2011 15:50:35 -0400 (EDT) To: Maria.L.Wilson-1@nasa.gov cc: Scott Marlowe , "Wilson, Maria Louise (LARC-E301)[SCIENCE SYSTEMS AND APPLICATIONS, INC]" , "pgsql-admin@postgresql.org" Subject: Re: log timestamp since daylight saving time In-reply-to: <4D7FAE47.3000503@nasa.gov> References: <4D7F6097.50708@nasa.gov> <4D7FABFC.6030809@nasa.gov> <4D7FAE47.3000503@nasa.gov> Comments: In-reply-to "Maria L. Wilson" message dated "Tue, 15 Mar 2011 14:21:59 -0400" Date: Tue, 15 Mar 2011 15:50:34 -0400 Message-ID: <3503.1300218634@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=-1.91 tagged_above=-10 required=5 tests=BAYES_00=-1.9, T_RP_MATCHES_RCVD=-0.01 X-Spam-Level: X-Archive-Number: 201103/177 X-Sequence-Number: 37049 "Maria L. Wilson" writes: > yes they are all running the same postgres version. - 8.4.5 > just as a test this morning - on one of the problem machines, we > installed another postgres installation - same version - just pointed it > to different paths - copied over the conf files and brought the server > up. This time it was the correct timeszone - US/Eastern. The other > postgres is set to EST5EDT. When I try to set it to US/Eastern, I get > an error... > postgres=# set timezone = 'US/Eastern'; > ERROR: unrecognized time zone name: "US/Eastern" Huh. That should most certainly work in a standard Postgres installation. You're apparently missing that timezone file. There are two possibilities: 1. If Postgres was built to use its own timezone database (the default), then $INSTALLPREFIX/share/timezone/US/Eastern is missing. Which means you've got an incomplete PG installation. 2. If Postgres was built with --with-system-tzdata=SOMETHING, then SOMETHING/US/Eastern is missing, which means either an incomplete system timezone database or whoever did the build used the wrong value of SOMETHING for your platform. I'd imagine that the EST5EDT setting you're seeing is some kind of fallback behavior upon not finding the proper timezone file. It's hard to be sure about where that came from without knowing exactly what's missing. regards, tom lane