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

From Tom Lane
Subject Re: Encoding/collation question
Date
Msg-id 25766.1576157753@sss.pgh.pa.us
Whole thread Raw
In response to Re: Encoding/collation question  (Karsten Hilbert <Karsten.Hilbert@gmx.net>)
Responses Re: Encoding/collation question
List pgsql-general
Karsten Hilbert <Karsten.Hilbert@gmx.net> writes:
> Question: is C collation expected to be future-proof /
> rock-solid /stable -- like UTF8 for encoding choice -- or
> could it end up like the SQL-ASCII encoding did: Yeah, we
> support it, it's been in use a long time, it should work,
> but, nah, one doesn't really want to choose it over UTF8 if
> at all possible, or at least know *exactly* what one is doing
> and BTW YMMV ?

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.

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

            regards, tom lane



pgsql-general by date:

Previous
From: Karsten Hilbert
Date:
Subject: Re: Encoding/collation question
Next
From: Rich Shepard
Date:
Subject: Re: Encoding/collation question