Search Postgresql Archives

locale and performance?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hello,
in the documentation is written that there'a a perfomrance impact if
another locale than C or POSIX is used.
problem is that using the standard locale results in unusable order
results for languages with spcial chars. in my example "umlauts" in
german.

it isn't acceptable to use the database without indexes if another
locale is used. are custom operator classes as described in the manual
as high-performance as the native index? are there any examples how to
use them in my case?

are there any tests that show how the performance decreases if another
locale is used? why is there a perfomance impact? it's a disappointing
that postgresql is only in one configuration to suply the max.
performance.

any tips or hints on that?

regards

Daniel


---------------------------(end of broadcast)---------------------------
TIP 5: don't forget to increase your free space map settings

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Postgresql Jobs]     [Postgresql Admin]     [Postgresql Performance]     [Linux Clusters]     [PHP Home]     [PHP on Windows]     [Kernel Newbies]     [PHP Classes]     [PHP Books]     [PHP Databases]     [Postgresql & PHP]     [Yosemite]
  Powered by Linux