Skip site navigation (1) Skip section navigation (2)

Re: BUG #3737: lower/upper fails to match extended chars in LATIN1

From: Heikki Linnakangas <heikki(at)enterprisedb(dot)com>
To: Jonas Forsman <jonas(dot)forsman(at)openit(dot)se>
Cc: PostgreSQL Bugs <pgsql-bugs(at)postgresql(dot)org>
Subject: Re: BUG #3737: lower/upper fails to match extended chars in LATIN1
Date: 2007-11-12 09:32:35
Message-ID: 47381DB3.9090204@enterprisedb.com (view raw or flat)
Thread:
Lists: pgsql-bugs
Jonas Forsman wrote:
> Recreating indicies is maybe not great but can be done quit easily compared
> to reinitializing a db or recoding an entire database.
> Sometimes a bit of a solution is all what it is needed. Would it be 
> possible
> to change the locale on the fly and only recreate indicies afterwards?

Hmm. I think you could change LC_CTYPE by just hacking the control file. 
LC_COLLATE would require the reindexing. Perhaps you could hack that as 
well, and then manually run REINDEX on all databases.

Did you confirm what the problem in your case really was? As Greg 
pointed out, the example query you posted was in fact flawed..

BTW, 8.3 is more strict on this, and won't allow you to initdb a cluster 
with mismatching locale and encoding.

-- 
   Heikki Linnakangas
   EnterpriseDB   http://www.enterprisedb.com

In response to

pgsql-bugs by date

Next:From: Euler Taveira de OliveiraDate: 2007-11-12 12:13:14
Subject: Re: BUG #3734: Invalid XML schema output.
Previous:From: Jonas ForsmanDate: 2007-11-12 09:17:16
Subject: Re: BUG #3737: lower/upper fails to match extended chars in LATIN1

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group