Message-ID: <4EBBF94E.4080401@serioustechnology.com>
Date: Thu, 10 Nov 2011 11:18:22 -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: Tom Lane <tgl@sss.pgh.pa.us>,
	"pgsql-admin@postgresql.org Admin" <pgsql-admin@postgresql.org>
Subject: Re: setting timezone
References: <4EBA7BCC.2030704@serioustechnology.com>
	<4EBA9C3D.9030701@pinpointresearch.com>
	<15278.1320857260@sss.pgh.pa.us>
	<4EBAD412.4060705@serioustechnology.com>
	<4EBAD75C.8030501@serioustechnology.com>
	<4EBADA14.3050608@pinpointresearch.com>
In-Reply-To: <4EBADA14.3050608@pinpointresearch.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Steve Crawford wrote:
> On 11/09/2011 11:41 AM, Geoffrey Myers wrote:
>> Geoffrey Myers wrote:
>>> Tom Lane wrote:
>>>> Steve Crawford <scrawford@pinpointresearch.com> writes:
>>>>> On 11/09/2011 05:10 AM, Geoffrey Myers wrote:
>>>>>> Is there a way to retain this information from the original 
>>>>>> database when reloading?
>>>>
>>>>> Time-zone setting is an attribute of the server configuration, not 
>>>>> of the data contained in the database.
>>>>
>>>> In particular, pg_dump doesn't know anything about postgresql.conf.
>>>> It's up to you to copy the server's configuration files.
>>>>
>>>>             regards, tom lane
>>>
>>> Thanks Tom, seems we were not setting it in the postgresql.conf file.
>>
>> What about the situation where you have two databases in the same 
>> cluster that need different timezones?  I'm assuming I would have to 
>> rely on setting it in each database, rather in the postgresql.conf file.
>>
>>>
>>
> 
> ALTER DATABASE foo SET TIMEZONE...

As I expected, thanks.

> 
> 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