Re: Encoding/collation question - Mailing list pgsql-general

From Andrew Gierth
Subject Re: Encoding/collation question
Date
Msg-id 875zimb0j8.fsf@news-spur.riddles.org.uk
Whole thread Raw
In response to Re: Encoding/collation question  (Rich Shepard <rshepard@appl-ecosys.com>)
Responses Re: Encoding/collation question
Re: Encoding/collation question
List pgsql-general
>>>>> "Rich" == Rich Shepard <rshepard@appl-ecosys.com> writes:

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

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.

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.

-- 
Andrew (irc:RhodiumToad)



pgsql-general by date:

Previous
From: Mike Lissner
Date:
Subject: Logical replication DNS cache
Next
From: Deepti Sharma S
Date:
Subject: RE: PostgreSQL version compatibility with RHEL7.7