Message-ID: <48517717.1020201@serioustechnology.com>
Date: Thu, 12 Jun 2008 15:20:55 -0400
From: Geoffrey <lists@serioustechnology.com>
User-Agent: Thunderbird 2.0.0.14 (X11/20080515)
MIME-Version: 1.0
To: Travis Smith <tsmith@optionshouse.com>
CC: Postgres-Admin list <pgsql-admin@postgresql.org>
Subject: Re: How is the default encoding determined
References: <48514CE1.8070803@serioustechnology.com>
	<D337038284820142B2A3196D1BFE2B47D7F03E@spswchi6mail1.peak6.net>
In-Reply-To: <D337038284820142B2A3196D1BFE2B47D7F03E@spswchi6mail1.peak6.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Travis Smith wrote:
> This looks like what you are looking for.
> 
> 
> 
> http://www.postgresql.org/docs/8.2/static/app-initdb.html
> 
> 
> The character set encoding can be set separately for a database when
> it is created. initdb determines the encoding for the template1
> database, which will serve as the default for all other databases. To
> alter the default encoding use the --encoding option. More details
> can be found in Section 21.2.

Thanks, I saw all that, what I was trying to figure out is where in the 
environment does initdb determine what to set the encoding to when it's 
not specified.

I ran into a problem with the wrong encoding on our database and I want 
to figure out if it's because the environment is different on this box, 
or if it was caused by the upgrade from 7.4 to 8.3

-- 
Until later, Geoffrey

Those who would give up essential Liberty, to purchase a little
temporary Safety, deserve neither Liberty nor Safety.
  - Benjamin Franklin