Re: database collation "C" and "C.LATIN1" - Mailing list pgsql-admin

From Tom Lane
Subject Re: database collation "C" and "C.LATIN1"
Date
Msg-id 374722.1678372549@sss.pgh.pa.us
Whole thread Raw
In response to Re: database collation "C" and "C.LATIN1"  (Laurenz Albe <laurenz.albe@cybertec.at>)
List pgsql-admin
Laurenz Albe <laurenz.albe@cybertec.at> writes:
> On Thu, 2023-03-09 at 08:37 +0000, James Pang (chaolpan) wrote:
>> Both follow  "C"  collate behavior ,right?  

> Right.

There is another difference: "C" is a built-in collation, while
"C.latin1" must have been something that initdb made because
"locale -a" claimed it exists on your platform.  Postgres has
some optimizations built in for "C" (and its equivalent "POSIX")
that will not apply for "C.latin1".  So while they should be
behaviorally the same, "C.latin1" is likely to be slower.

            regards, tom lane



pgsql-admin by date:

Previous
From: Sumit Sengupta
Date:
Subject: Re: postgresql to Oracle database migration
Next
From: Wells Oliver
Date:
Subject: Malformed array literal in goin from jsonb to real[]