Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1w0RKp-001uMC-1x for pgsql-hackers@arkaria.postgresql.org; Wed, 11 Mar 2026 21:43:20 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.96) (envelope-from ) id 1w0RKn-00C1SO-0o for pgsql-hackers@arkaria.postgresql.org; Wed, 11 Mar 2026 21:43:17 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1w0RKm-00C1SF-2i for pgsql-hackers@lists.postgresql.org; Wed, 11 Mar 2026 21:43:17 +0000 Received: from mail-qk1-x731.google.com ([2607:f8b0:4864:20::731]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.98.2) (envelope-from ) id 1w0RKk-00000002CYP-3ivZ for pgsql-hackers@postgresql.org; Wed, 11 Mar 2026 21:43:17 +0000 Received: by mail-qk1-x731.google.com with SMTP id af79cd13be357-8cd847b4b23so29343085a.0 for ; Wed, 11 Mar 2026 14:43:14 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=j-davis-com.20230601.gappssmtp.com; s=20230601; t=1773265393; x=1773870193; darn=postgresql.org; h=mime-version:user-agent:content-transfer-encoding:references :in-reply-to:date:cc:to:from:subject:message-id:from:to:cc:subject :date:message-id:reply-to; bh=ey9/YqYFPYYR1mhZIhu/aI680qghlyq5tzRXm0dY5RI=; b=q+UvElkok76UCpoKJWnuCFr4kM0LBm1unIBQQNa8TlZxYMpQQUT20l3/4nId+rOQBX KA3HLGmcq3B5+TE2ChEXSTS+cv0DE9d8FcgSKVki0kfMuTbyUuB3TMOJpezg3TQ62SR2 QvAhes7mNiM3jx8SNHD2BLVaHUTqv3gA53qRT/IHtfpkWzXeDswRJ4B9wfJLStp7Ee/A e7wzOGI4w2C3uM6vxFciq5lgoV9cLM3SHz1AlrpyVgHhUEjQaNY9z6B0qbcDqCgOUrIW ye6Jtn9Rmfo108D7mhVMwkvebydWsdLfwluBzYljOMUMiLAbVkf3jiywIz60OPbSQmK6 c+KQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1773265393; x=1773870193; h=mime-version:user-agent:content-transfer-encoding:references :in-reply-to:date:cc:to:from:subject:message-id:x-gm-gg :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=ey9/YqYFPYYR1mhZIhu/aI680qghlyq5tzRXm0dY5RI=; b=BiiQ/ums/KL5XSK64ZIBCSBwO63C9ipLLaSz6cDEsU97+h7aUSFmrNeyXyNxtsScM4 QLB8b8QDQkmX5DbUWxdgbK5lFLhhBzC7+7O4npEwuJ8JYX9fZbEgZsFMKUte4VeVHjjO SjjYBre2Iaai86I6996X2lC1Ww1YyKLXa6kkTR8VKBizWJK61Yabw/U8692phRosxGg+ BhnOhH9t3VlQUSugHP9GTr50M2ev+HNtKgJ3Mm7KwgArEMl16jNX2Qh/KYFQrFFqXuTS LiLjvW/Im/H7uF0dVr/+f8j+iMchh/pc5OHlkTnmJD+aBt7A26ztyDNvsevye0FWgdPX yRNg== X-Gm-Message-State: AOJu0YzMgHc6OCMH9AIffrMtB8M3eIliiPFcUtMAZQiOfkn77KnHUNM8 MWc4Iz6AUgMUTyGeSlG9V/somuOCN0GSsfow/G0pYnUqimaPS8yDC0K18CgFK5fe5w== X-Gm-Gg: ATEYQzxLJVm+qJWkuDd4vObWIsM26VyrvWVUyG+VwOZbI9hKnr9G/N+SqefoU4Mxqs6 Yr98ocvujtEndQ+6E7vDoFr6XWRcldyXtDFFtv0DTmNvn6o4HUPutE2psbcN66RQUUSSW+a7p/I 6hPdg0VmlMCy2Cu38toT2loVMyhacNodoJHDjsrFiPs12LMq3b2O8zfNY6YP0nV/FzRAtrjxHZp RolrIkmtrd3NSBxO0EDxf+3TopM9AaaQOYOA2yADKIuZeptcCS25PQSe4yzHS2sDBajAFBW5aZM pFgD0plgcXpDXmOI93zwKnDtIx6ruilBN286XUMLvY5Yfe54zjVtiP429c66eAsqEkLWSshmP2G C+trDo9ZpoeXxos0jNEsccBTeItzhkIXX0dpIPjXxkK1pseK7tBFM6GN2oUeNAzUtV5UpvRZsA2 KkPOyiYHBtU2vFLAKOL9dX X-Received: by 2002:a05:620a:bc5:b0:8cd:9b31:23ab with SMTP id af79cd13be357-8cda1ac1213mr515754385a.61.1773265393096; Wed, 11 Mar 2026 14:43:13 -0700 (PDT) Received: from [10.10.244.3] ([50.175.226.10]) by smtp.gmail.com with ESMTPSA id af79cd13be357-8cda1ff7642sm234665685a.21.2026.03.11.14.43.12 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Wed, 11 Mar 2026 14:43:12 -0700 (PDT) Message-ID: Subject: Re: Change initdb default to the builtin collation provider From: Jeff Davis To: Laurenz Albe , Robert Haas Cc: pgsql-hackers@postgresql.org Date: Wed, 11 Mar 2026 14:43:11 -0700 In-Reply-To: <138f54d51a4baffa3e4f80d68d814e7bf3d99716.camel@cybertec.at> References: <47e1b4f72fe732c5ae85c6cf2c085b4e99a10120.camel@j-davis.com> <4309879ac305b1cf6b4d7b5fb85bc7b62c6ab768.camel@j-davis.com> <138f54d51a4baffa3e4f80d68d814e7bf3d99716.camel@cybertec.at> Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable User-Agent: Evolution 3.52.3-0ubuntu1.1 MIME-Version: 1.0 List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On Wed, 2026-03-11 at 21:05 +0100, Laurenz Albe wrote: > The big advantage: if you have only two or three indexes in your > database that are sorted in a collation other than C, the likelihood > for index corruption will be way lower.=C2=A0 For example, the unique > constraint on your part number column that contains values like > 'XY-1-13*' or '*P1-12_A' (which are pretty likely to be affected by > the subtle changes in libc collations) will be sorted in the C > collation, which is just fine for everybody. Agreed. The collation problems are not because it's used in the handful of indexes where it's useful; the problems happen when it's used everywhere. If a collation version change is detected, and a few indexes need to be REINDEXed, I think users understand that. But it's pretty difficult to explain to a user that all text indexes (including primary keys) need to be reindexed, and that there's no way to keep track of what still needs to be done. Regards, Jeff Davis