Re: Encoding/collation question

From: Rich Shepard <rshepard(at)appl-ecosys(dot)com>
To: pgsql-general(at)lists(dot)postgresql(dot)org
Subject: Re: Encoding/collation question
Date: 2019-12-11 19:44:29
Message-ID: alpine.LNX.2.20.1912111142310.10822@salmo.appl-ecosys.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Wed, 11 Dec 2019, Tom Lane wrote:

> String comparisons in non-C collations tend to be a lot slower than they
> are in C collation. Whether this makes a noticeable difference to you
> depends on your workload, but certainly we've seen performance gripes that
> trace to that.

Tom,

How interesting.

> If your data doesn't require the larger character set of UTF8, then using
> LATIN-any is going to offer some space savings (for non-ASCII characters)
> plus minor performance benefits due to the lack of variable-width
> characters. This is less significant than the collation issue, though, for
> most people.

I doubt that my use will notice meaningful differences. Since there are only
two or three databases in UTF8 and its collation perhaps I'll convert those
to LATIN1 and C.

Thanks for the insights.

Regards,

Rich

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Rich Shepard 2019-12-11 20:54:29 Counting number of sites with same number of sampling dates
Previous Message Tom Lane 2019-12-11 19:25:17 Re: Encoding/collation question