Message-ID: <4EBAD341.6040006@serioustechnology.com>
Date: Wed, 09 Nov 2011 14:23:45 -0500
From: Geoffrey Myers <lists@serioustechnology.com>
User-Agent: Thunderbird 2.0.0.24 (X11/20110928)
MIME-Version: 1.0
To: Steve Crawford <scrawford@pinpointresearch.com>
CC: Geoffrey Myers <lists@serioustechnology.com>, pgsql-admin@postgresql.org
Subject: Re: setting timezone
References: <4EBA7BCC.2030704@serioustechnology.com>
	<4EBA9C3D.9030701@pinpointresearch.com>
In-Reply-To: <4EBA9C3D.9030701@pinpointresearch.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Steve Crawford wrote:
> On 11/09/2011 05:10 AM, Geoffrey Myers wrote:
>> We are moving a number of databases to new hardware.  Some of these 
>> machines have the timezone set in the database differently then the 
>> actual location of the machine as they are access from a different 
>> timezone.  We were surprised to note that when we dump the database 
>> and reloaded it on the new machine, it did not retain the timezone 
>> setting.
>>
>> Is there a way to retain this information from the original database 
>> when reloading?
>>
>> Thanks.
>>
> 
> Time-zone setting is an attribute of the server configuration, not of 
> the data contained in the database. Unless overidden by the timezone 
> setting in postgresql.conf, PostgreSQL will use the server's time zone 
> environment setting. You can specify a default time-zone for PostgreSQL 
> independent of the server's environment by setting "timezone" explicitly 
> in postgresql.conf.
> 
> Clients can override the default server setting with "SET TIMEZONE TO 
> ...;" which is useful when a single server is supporting users across 
> many time zones.

Thanks, that's just what I needed.

> 
> Cheers,
> Steve
> 
> 


-- 
Until later, Geoffrey

"I predict future happiness for America if they can prevent
the government from wasting the labors of the people under
the pretense of taking care of them."
- Thomas Jefferson