RE: database collation "C" and "C.LATIN1"
От | James Pang (chaolpan) |
---|---|
Тема | RE: database collation "C" and "C.LATIN1" |
Дата | |
Msg-id | PH0PR11MB51911F9E21AB40CEE460886DD6B59@PH0PR11MB5191.namprd11.prod.outlook.com обсуждение исходный текст |
Ответ на | Re: database collation "C" and "C.LATIN1" (Laurenz Albe <laurenz.albe@cybertec.at>) |
Список | pgsql-admin |
The sorting order behavior is same ,right? -----Original Message----- From: Laurenz Albe <laurenz.albe@cybertec.at> Sent: Thursday, March 9, 2023 4:30 PM To: James Pang (chaolpan) <chaolpan@cisco.com>; pgsql-admin@lists.postgresql.org Subject: Re: database collation "C" and "C.LATIN1" 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 onlybe used with encoding LATIN1 (8). The behavior is the same. Yours, Laurenz Albe
В списке pgsql-admin по дате отправления: