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 1k8OZc-0008Ll-MF for pgsql-novice@arkaria.postgresql.org; Wed, 19 Aug 2020 13:56:16 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1k8OZb-00033k-JG for pgsql-novice@arkaria.postgresql.org; Wed, 19 Aug 2020 13:56:15 +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 1k8OZb-0002oI-D1 for pgsql-novice@lists.postgresql.org; Wed, 19 Aug 2020 13:56:15 +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 1k8OZV-0005tY-Rm for pgsql-novice@postgresql.org; Wed, 19 Aug 2020 13:56:14 +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 07JDu6LI1401864; Wed, 19 Aug 2020 09:56:06 -0400 From: Tom Lane To: marcelo mendoza cc: Laurenz Albe , pgsql-novice@postgresql.org Subject: Re: Change collate postgresql In-reply-to: References: <196166551a133215f5f3f7510f1403c82c774bff.camel@cybertec.at> Comments: In-reply-to marcelo mendoza message dated "Wed, 19 Aug 2020 09:06:52 -0400" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <1401862.1597845366.1@sss.pgh.pa.us> Date: Wed, 19 Aug 2020 09:56:06 -0400 Message-ID: <1401863.1597845366@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk marcelo mendoza writes: > Hi Laurenz, this is the space en_US.UTF- 8 (the space is before the 8) > Collate | en_US.UTF- > | 8 > The database was created in this way, without error, how can I fix this? I'm guessing that you specified LC_COLLATE that way when you created the database. Postgres won't complain if setlocale() doesn't, which it very possibly wouldn't. I don't believe we offer any DDL command to change that, so a direct UPDATE on pg_database is the only way. Should be pretty harmless as long as you don't try to change the setting to a functionally different value. regards, tom lane