From: Tom Lane <tgl@sss.pgh.pa.us>
To: Deron <fecastle@gmail.com>
cc: pgsql-admin@postgresql.org
Subject: Re: Timezone from PG8 to PG9
In-reply-to: 
 <CAF3Lvs6hp=fN4Bx9vpeLvA=cgqJo3iNB4kETiD9inkRkkY0mhw@mail.gmail.com>
References: 
 <CAF3Lvs6hp=fN4Bx9vpeLvA=cgqJo3iNB4kETiD9inkRkkY0mhw@mail.gmail.com>
Comments: In-reply-to Deron <fecastle@gmail.com>
 message dated "Fri, 20 Dec 2013 14:29:13 -0800"
Date: Fri, 20 Dec 2013 19:11:01 -0500
Message-ID: <25616.1387584661@sss.pgh.pa.us>
Precedence: bulk
Sender: pgsql-admin-owner@postgresql.org

Deron <fecastle@gmail.com> writes:
> Hello we were upgrading a test system from PG8.3.6 to PG 9.3 and it appears
> as though the timezone is not set on the new PG9.3.   I should say that we
> never did set the timezone for PG8, but somehow the PG server knew the
> 'localtime' of the system:

> show timezone;
>   TimeZone
> ------------
>  US/Eastern
> (1 row)

> However, after upgrading to PG9:
> show timezone;
>  TimeZone
> ----------
>  GMT
> (1 row)

> We saw the same for US/Pacific zone as well.

> We do set /etc/localtime for the local timezone of the box.  We can
> configure this in the postgresql.conf file.   It does appear as though PG9
> server reads /etc/localtime on startup, but it is not set.

IIRC, we moved the determination of the default timezone into initdb
somewhere along the line; so what matters now is the system environment
initdb saw, not what the server sees on start.  If you don't like what
you're getting, change it in postgresql.conf.

			regards, tom lane


-- 
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin