1
0
mirror of https://github.com/postgres/postgres.git synced 2025-12-21 05:21:08 +03:00

Add mention of performance impact on LIKE of non-C locales.

This commit is contained in:
Bruce Momjian
2005-01-04 00:05:45 +00:00
parent a2a5526ecb
commit 246be304a5
3 changed files with 34 additions and 23 deletions

View File

@@ -1,4 +1,4 @@
<!-- $PostgreSQL: pgsql/doc/src/sgml/charset.sgml,v 2.47 2004/12/27 22:30:10 tgl Exp $ -->
<!-- $PostgreSQL: pgsql/doc/src/sgml/charset.sgml,v 2.48 2005/01/04 00:05:44 momjian Exp $ -->
<chapter id="charset">
<title>Localization</>
@@ -189,10 +189,10 @@ initdb --locale=sv_SE
</sect2>
<sect2>
<title>Benefits</>
<title>Behavior</>
<para>
Locale support influences in particular the following features:
Locale support influences the following features:
<itemizedlist>
<listitem>
@@ -202,6 +202,13 @@ initdb --locale=sv_SE
</para>
</listitem>
<listitem>
<para>
The ability to use indexes with <literal>LIKE</> clauses
<indexterm><primary>LIKE</><secondary>and locales</></indexterm>
</para>
</listitem>
<listitem>
<para>
The <function>to_char</> family of functions
@@ -211,9 +218,11 @@ initdb --locale=sv_SE
</para>
<para>
The only severe drawback of using the locale support in
<productname>PostgreSQL</> is its speed. So use locales only if
you actually need them.
The drawback of using locales other than <literal>C</> or
<literal>POSIX</> in <productname>PostgreSQL</> is its performance
impact. It slows character handling and prevents ordinary indexes
from being used by <literal>LIKE</>. For this reason use locales
only if you actually need them.
</para>
</sect2>