pg.ddx.io pgsql-performance@postgresql.org mailing list archive
help / color / mirror / Atom feedperformance impact of non-C locale
4+ messages / 2 participants
[nested] [flat]
* performance impact of non-C locale
@ 2008-09-07 10:50 Axel Rau <Axel.Rau@chaos1.de>
0 siblings, 1 reply; 4+ messages in thread
From: Axel Rau @ 2008-09-07 10:50 UTC (permalink / raw)
To: pgsql-performance
Hi everyone,
some erp software requires a change of my pgsql cluster from
locale C encoding UTF-8
to
locale de_DE.UTF-8 encoding UTF-8
Most of my databases have only ASCII text data (8 bit UTF8 code range)
in the text columns.
Does the above change influence index performance on such columns?
Does postmaster keep track on any multibyte characters being inserted
in such columns, so that the planner can adapt?
What other performance impacts can be expected?
Axel
---
^ permalink raw reply [nested|flat] 4+ messages in thread
* Re: performance impact of non-C locale
@ 2008-09-11 09:29 Peter Eisentraut <peter_e@gmx.net>
parent: Axel Rau <Axel.Rau@chaos1.de>
0 siblings, 1 reply; 4+ messages in thread
From: Peter Eisentraut @ 2008-09-11 09:29 UTC (permalink / raw)
To: Axel Rau <Axel.Rau@chaos1.de>; +Cc: pgsql-performance
Axel Rau wrote:
> some erp software requires a change of my pgsql cluster from
> locale C encoding UTF-8
> to
> locale de_DE.UTF-8 encoding UTF-8
>
> Most of my databases have only ASCII text data (8 bit UTF8 code range)
> in the text columns.
> Does the above change influence index performance on such columns?
Yes.
> Does postmaster keep track on any multibyte characters being inserted in
> such columns, so that the planner can adapt?
No.
> What other performance impacts can be expected?
The performance impact is mainly with string comparisons and sorts. I
suggest you run your own tests to find out what is acceptable in your
scenario.
^ permalink raw reply [nested|flat] 4+ messages in thread
* Re: performance impact of non-C locale
@ 2008-09-11 09:57 Axel Rau <Axel.Rau@chaos1.de>
parent: Peter Eisentraut <peter_e@gmx.net>
0 siblings, 1 reply; 4+ messages in thread
From: Axel Rau @ 2008-09-11 09:57 UTC (permalink / raw)
To: Peter Eisentraut <peter_e@gmx.net>; +Cc: pgsql-performance
Am 11.09.2008 um 11:29 schrieb Peter Eisentraut:
>>
>> What other performance impacts can be expected?
>
> The performance impact is mainly with string comparisons and sorts.
> I suggest you run your own tests to find out what is acceptable in
> your scenario.
Im not yet convinced to switch to non-C locale. Is the following
intended behavior:
With lc_ctype C: select lower('ÄÖÜ'); => ÄÖÜ
With lc_ctype en_US.utf8 select lower('ÆÅË'); => æåë
? (Both have server encoding UTF8)
Axel
---
^ permalink raw reply [nested|flat] 4+ messages in thread
* Re: performance impact of non-C locale
@ 2008-09-11 10:33 Peter Eisentraut <peter_e@gmx.net>
parent: Axel Rau <Axel.Rau@chaos1.de>
0 siblings, 0 replies; 4+ messages in thread
From: Peter Eisentraut @ 2008-09-11 10:33 UTC (permalink / raw)
To: Axel Rau <Axel.Rau@chaos1.de>; +Cc: pgsql-performance
Axel Rau wrote:
> Im not yet convinced to switch to non-C locale. Is the following
> intended behavior:
> With lc_ctype C: select lower('ÄÖÜ'); => ÄÖÜ
> With lc_ctype en_US.utf8 select lower('ÆÅË'); => æåë
> ? (Both have server encoding UTF8)
I would expect exactly that.
^ permalink raw reply [nested|flat] 4+ messages in thread
end of thread, other threads:[~2008-09-11 10:33 UTC | newest]
Thread overview: 4+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2008-09-07 10:50 performance impact of non-C locale Axel Rau <Axel.Rau@chaos1.de>
2008-09-11 09:29 ` Peter Eisentraut <peter_e@gmx.net>
2008-09-11 09:57 ` Axel Rau <Axel.Rau@chaos1.de>
2008-09-11 10:33 ` Peter Eisentraut <peter_e@gmx.net>
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox