From: Laurenz Albe <laurenz.albe@cybertec.at>
To: James Pang (chaolpan) <chaolpan@cisco.com>
To: pgsql-admin@lists.postgresql.org <pgsql-admin@lists.postgresql.org>
Subject: Re: database collation "C" and "C.LATIN1"
Date: Thu, 09 Mar 2023 09:29:43 +0100
Message-ID: <9ba3e513009bada4845128d4db349346d0f956db.camel@cybertec.at> (raw)
In-Reply-To: <PH0PR11MB51911905C6D8C753E98504FCD6B59@PH0PR11MB5191.namprd11.prod.outlook.com>
References: <PH0PR11MB51911905C6D8C753E98504FCD6B59@PH0PR11MB5191.namprd11.prod.outlook.com>
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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: laurenz.albe@cybertec.at, chaolpan@cisco.com, pgsql-admin@lists.postgresql.org
Subject: Re: database collation "C" and "C.LATIN1"
In-Reply-To: <9ba3e513009bada4845128d4db349346d0f956db.camel@cybertec.at>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox