Thread: Question to localization
Hello,
I have a question to the usage of locale.
In the PostgreSQL 8.0.3 Documentation is written:
"The drawback of using locales other than C or POSIX in PostgreSQL is its performance impact. It slows character handling and prevents ordinary indexes from being used by LIKE. For this reason use locales only if you actually need them. "
Is there a general perfomance deficit, when using locales or only when using LIKE?
Regards
Michaela
"MG" <pgsql-admin@carladata.de> writes: > In the PostgreSQL 8.0.3 Documentation is written: > "The drawback of using locales other than C or POSIX in PostgreSQL is = > its performance impact. It slows character handling and prevents = > ordinary indexes from being used by LIKE. For this reason use locales = > only if you actually need them. " > Is there a general perfomance deficit, when using locales or only when = > using LIKE? The locale setting affects every comparison of text values (the documentation is poorly written on this point, because it mentions only ORDER BY). So if you use text (or varchar or char) keys in your tables, you'll probably see a noticeable performance hit from using a non-C locale. If you tend to use integer keys then you might not notice any difference. regards, tom lane