From: Josh Berkus <josh@agliodbs.com>
Reply-To: josh@agliodbs.com
Organization: Aglio Database Solutions
To: Peter Eisentraut <peter_e@gmx.net>
Subject: Re: Doc patch needed: encodings?
Date: Mon, 6 Dec 2004 10:39:17 -0800
User-Agent: KMail/1.6.2
Cc: PostgreSQL Docs <pgsql-docs@postgresql.org>
References: <200412051546.53124.josh@agliodbs.com>
	<200412060923.02772.josh@agliodbs.com>
	<200412061919.21637.peter_e@gmx.net>
In-Reply-To: <200412061919.21637.peter_e@gmx.net>
MIME-Version: 1.0
Content-Disposition: inline
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Message-Id: <200412061039.17201.josh@agliodbs.com>

Peter,

> Linux distributions have been shipping with non-C locale settings for a
> long, long time, so that complaint would be invalid. 

In US distributions it's a recent thing.   The switch to non-C locales is a 
recent thing; RH Enterprise 3.0, and SuSE 9.0.  But I expect in Europe you've 
been using non-C locales for a while.

I'd like to have an explanation of this somewhere else newbies are liable to 
read it, *before* their first production "LIKE" query doesn't use an index.  
Where would be appropriate?

And, for English speakers, what exactly is wrong with using 'C' locale instead 
of the environment one?

-- 
--Josh

Josh Berkus
Aglio Database Solutions
San Francisco