Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1paHN8-0002OT-8J for pgsql-admin@arkaria.postgresql.org; Thu, 09 Mar 2023 14:35:58 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1paHN7-0000pW-2A for pgsql-admin@arkaria.postgresql.org; Thu, 09 Mar 2023 14:35:57 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1paHN6-0000pN-O4 for pgsql-admin@lists.postgresql.org; Thu, 09 Mar 2023 14:35:56 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1paHN4-0006Qv-Ab for pgsql-admin@lists.postgresql.org; Thu, 09 Mar 2023 14:35:55 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.15.2/8.15.2) with ESMTP id 329EZngw374723; Thu, 9 Mar 2023 09:35:49 -0500 From: Tom Lane To: Laurenz Albe cc: "James Pang (chaolpan)" , "pgsql-admin@lists.postgresql.org" Subject: Re: database collation "C" and "C.LATIN1" In-reply-to: <5a8c87da0b8b61afd6ce12bb5cd37e87227dc7f1.camel@cybertec.at> References: <9ba3e513009bada4845128d4db349346d0f956db.camel@cybertec.at> <5a8c87da0b8b61afd6ce12bb5cd37e87227dc7f1.camel@cybertec.at> Comments: In-reply-to Laurenz Albe message dated "Thu, 09 Mar 2023 13:04:34 +0100" MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-ID: <374721.1678372549.1@sss.pgh.pa.us> Content-Transfer-Encoding: 8bit Date: Thu, 09 Mar 2023 09:35:49 -0500 Message-ID: <374722.1678372549@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Laurenz Albe 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