From: Peter Eisentraut <peter_e@gmx.net>
To: josh@agliodbs.com
Subject: Re: Doc patch needed: encodings?
Date: Mon, 6 Dec 2004 20:02:43 +0100
User-Agent: KMail/1.6.2
Cc: PostgreSQL Docs <pgsql-docs@postgresql.org>
References: <200412051546.53124.josh@agliodbs.com>
	<200412061919.21637.peter_e@gmx.net>
	<200412061039.17201.josh@agliodbs.com>
In-Reply-To: <200412061039.17201.josh@agliodbs.com>
MIME-Version: 1.0
Content-Disposition: inline
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 8bit
Message-Id: <200412062002.43906.peter_e@gmx.net>

Josh Berkus wrote:
> 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.

I have it on record that Red Hat has set a non-C locale by default at 
least since Red Hat 6.1 as distributed in North America (aren't they 
the same anyway?) in 1999.  I know that because we had this exact 
discussion back then.

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

Near the documentation of "LIKE".

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

It makes it difficult to write a résumé, to name one thing.

-- 
Peter Eisentraut
http://developer.postgresql.org/~petere/