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

From Karsten Hilbert
Subject Re: Encoding/collation question
Date
Msg-id 20191218093735.GA472@hermes.hilbert.loc
Whole thread Raw
In response to Re: Encoding/collation question  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-general
On Thu, Dec 12, 2019 at 08:35:53AM -0500, Tom Lane wrote:

> C collation basically devolves to strcmp/memcmp, which are as standard
> and well-defined as can be.  If you're happy with the way it sorts
> things then there's no reason not to use it.

So that's the collation to use when "technical" sorting is
required (say, when uniqueness does not depend on the notion
of culturally equivalent characters).

> It's actually all the *other* collations where you should worry about
> their behavior being a moving target :-(.

But then that is to be expected.

Thanks,
Karsten
--
GPG  40BE 5B0E C98E 1713 AFA6  5BC0 3BEA AC80 7D4F C89B



pgsql-general by date:

Previous
From: Thomas Munro
Date:
Subject: Re: Row locks, SKIP LOCKED, and transactions
Next
From: Steven Winfield
Date:
Subject: RE: Row locks, SKIP LOCKED, and transactions