C locale versus en_US.UTF8. (Was: String comparision in PostgreSQL)

Поиск
Список
Период
Сортировка
От Aleksey Tsalolikhin
Тема C locale versus en_US.UTF8. (Was: String comparision in PostgreSQL)
Дата
Msg-id CA+jMWoe75vgMaJ3WU0t5H6i+Tt6B_MV+Vva6ktkPbr=hWjxung@mail.gmail.com
обсуждение исходный текст
Ответы Re: C locale versus en_US.UTF8. (Was: String comparision in PostgreSQL)  (Bruce Momjian <bruce@momjian.us>)
Re: C locale versus en_US.UTF8. (Was: String comparision in PostgreSQL)  (Peter Eisentraut <peter_e@gmx.net>)
Список pgsql-general
On Wed, Aug 29, 2012 at 9:45 AM, Merlin Moncure <mmoncure@gmail.com> wrote:
> citext unfortunately doesn't allow for index optimization of LIKE
> queries, which IMNSHO defeats the whole purpose.  to the best way
> remains to use lower() ...
> this will be index optimized and fast as long as you specified C
> locale for your database.

What is the difference between C and en_US.UTF8, please?  We see that
the same query (that invokes a sort) runs 15% faster under the C
locale.  The output between C and en_US.UTF8 is identical.  We're
considering moving our database from en_US.UTF8 to C, but we do deal
with internationalized text.

Best,
Aleksey


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

Предыдущее
От: Moshe Jacobson
Дата:
Сообщение: Re: Dropping a column on parent table doesn't propagate to children?
Следующее
От: "Little, Douglas"
Дата:
Сообщение: psql & unix env variables