Re: bug: LC_CTYPE=en_US.UTF-8 confuses query planner

Поиск
Список
Период
Сортировка
От Tom Lane
Тема Re: bug: LC_CTYPE=en_US.UTF-8 confuses query planner
Дата
Msg-id 15235.1119970118@sss.pgh.pa.us
обсуждение исходный текст
Ответ на bug: LC_CTYPE=en_US.UTF-8 confuses query planner  (Dmitry Karasik <dk@catpipe.net>)
Список pgsql-hackers
Dmitry Karasik <dk@catpipe.net> writes:
> When database is initdb'ed with LC_CTYPE=C, the query uses index
> scan; when LC_CTYPE=en_US.UTF-8 it is the sequential scan.

This is in the FAQ:    When using wild-card operators such as LIKE or ~, indexes can only be  used in certain
circumstances:     ...    * The default C locale must be used during initdb because it is not      possible to know the
next-greatestcharacter in a non-C locale.      You can create a special text_pattern_ops index for such cases      that
workonly for LIKE indexing.
 
        regards, tom lane


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

Предыдущее
От: Tom Lane
Дата:
Сообщение: Re: initdb -W failure with role-capable catalogs
Следующее
От: Pavel Stehule
Дата:
Сообщение: Re: Implementing SQL/PSM for PG 8.2 - debugger