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

Поиск
Список
Период
Сортировка
От Heikki Linnakangas
Тема Re: BUG #3737: lower/upper fails to match extended chars in LATIN1
Дата
Msg-id 47381DB3.9090204@enterprisedb.com
обсуждение исходный текст
Ответ на BUG #3737: lower/upper fails to match extended chars in LATIN1  ("Jonas Forsman" <jonas@axier.org>)
Список 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

В списке pgsql-bugs по дате отправления:

Предыдущее
От: Dave Page
Дата:
Сообщение: Re: BUG #3744: libpq.a missed from /lib directory
Следующее
От: Jonas Forsman
Дата:
Сообщение: Re: BUG #3737: lower/upper fails to match extended chars in LATIN1