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

From Laurenz Albe
Subject Re: database collation "C" and "C.LATIN1"
Date
Msg-id 9ba3e513009bada4845128d4db349346d0f956db.camel@cybertec.at
Whole thread Raw
In response to database collation "C" and "C.LATIN1"  ("James Pang (chaolpan)" <chaolpan@cisco.com>)
Responses RE: database collation "C" and "C.LATIN1"  ("James Pang (chaolpan)" <chaolpan@cisco.com>)
RE: database collation "C" and "C.LATIN1"  ("James Pang (chaolpan)" <chaolpan@cisco.com>)
List pgsql-admin
On Thu, 2023-03-09 at 08:22 +0000, James Pang (chaolpan) wrote:
> We create one database with collate= “C.LATIN1”, any difference between “C” and “C.LATIN1” ?
> database encoding is “LATIN1”.
>  
>   oid  |        collname        | collencoding |   collcollate    |    collctype     | collversion
> -------+------------------------+--------------+------------------+------------------+-------------
>    950 | C                      |           -1 | C                | C                |
>  12328 | C.latin1               |            8 | C.latin1         | C.latin1         |

The difference is a technicality: "C" is encoding agnostic (-1) and can be used with
any encoding, while "C.latin1" can only be used with encoding LATIN1 (8).
The behavior is the same.

Yours,
Laurenz Albe

pgsql-admin by date:

Previous
From: "James Pang (chaolpan)"
Date:
Subject: database collation "C" and "C.LATIN1"
Next
From: "James Pang (chaolpan)"
Date:
Subject: RE: database collation "C" and "C.LATIN1"