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-12 13:37:59
Message-ID: alpine.LNX.2.20.1912120536320.8975@salmo.appl-ecosys.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Thu, 12 Dec 2019, Andrew Gierth wrote:

> Note that it's perfectly fine to use UTF8 encoding and C collation (this
> has the effect of sorting strings in Unicode codepoint order); this is as
> fast for comparisons as LATIN1/C is.

Andrew,

This is really useful insight. I've not thought of the relationship of
encoding to collation (which I now know there isn't.)

> For those cases where you need data to be sorted in a
> culturally-meaningful order rather than in codepoint order, you can set
> collations on specific columns or in individual queries.

Not an issue for my work. :-)

Thanks very much,

Rich

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Peter Eisentraut 2019-12-12 14:19:14 Re: Logical replication DNS cache
Previous Message Tom Lane 2019-12-12 13:35:53 Re: Encoding/collation question