Skip site navigation (1) Skip section navigation (2)

Re: Question to localization

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "MG" <pgsql-admin(at)carladata(dot)de>
Cc: pgsql-admin(at)postgresql(dot)org
Subject: Re: Question to localization
Date: 2005-08-31 14:47:13
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-admin
"MG" <pgsql-admin(at)carladata(dot)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

In response to

pgsql-admin by date

Next:From: Chris TraversDate: 2005-08-31 16:33:30
Subject: Re: Replication
Previous:From: Alvaro HerreraDate: 2005-08-31 14:40:09
Subject: Re: auto vacuum settings

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group