[prev in list] [next in list] [prev in thread] [next in thread] 

List:       postgresql-admin
Subject:    Re: [ADMIN] Question to localization
From:       Tom Lane <tgl () sss ! pgh ! pa ! us>
Date:       2005-08-31 14:47:13
Message-ID: 1857.1125499633 () sss ! pgh ! pa ! us
[Download RAW message or body]

"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

---------------------------(end of broadcast)---------------------------
TIP 9: In versions below 8.0, the planner will ignore your desire to
       choose an index scan if your joining column's datatypes do not
       match
[prev in list] [next in list] [prev in thread] [next in thread]