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 1wTGX8-000Q4M-2i for pgsql-pkg-debian@arkaria.postgresql.org; Sat, 30 May 2026 10:03:10 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.96) (envelope-from ) id 1wTGX7-005rX4-0C for pgsql-pkg-debian@arkaria.postgresql.org; Sat, 30 May 2026 10:03:09 +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 1wTGX6-005rWw-2C for pgsql-pkg-debian@lists.postgresql.org; Sat, 30 May 2026 10:03:09 +0000 Received: from smtp.osfda.org ([93.190.142.111]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.98.2) (envelope-from ) id 1wTGX2-00000000I4G-26Zl for pgsql-pkg-debian@lists.postgresql.org; Sat, 30 May 2026 10:03:08 +0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=osfda.org; s=default; t=1780135382; bh=ttHYKmctu8oq6zlCBV7JJ1xRySRlqhoXnD2G/7CwNWA=; h=Date:To:From:Subject:From; b=w2W0cvvbgGetKvqcE14hegRlqEBFBY3yIOT5Hla7tmG+HZC1YBr1XShmQo5V/LV11 /YaRKg3IjI44EZnIy3R8qn1SBP6YWG1oH1cH7+opuviaQqjEVsh77vZicHnjyD810a 6EZDhsPJit7jbp4sXKBEprGroJHmMFrpa2DaQSVhmNXWu7W9TL4kH6Ad0katnpRy7K HhoFNd2AoGoXY5V2lAYfxiNY0AgVN4l9UiiL2bxg8Kyqq2vJZZNhd2v88W5ohmlw2U ObaNrMV2gjfFfzNUymDrdMxJdje0eYmTcdORPyD1lvejDPDx9sQhBSsgmaXKo82f9z pWmeTPrVckZ1A== Received: from [192.168.1.173] (pool-68-132-226-133.nycmny.fios.verizon.net [68.132.226.133]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange x25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by smtp.osfda.org (MTA) with ESMTPSA id 4912015C036F for ; Sat, 30 May 2026 12:03:02 +0200 (CEST) Content-Type: multipart/alternative; boundary="------------CfMHVazTjSFscsaVjStT5CD4" Message-ID: <147d06e3-0858-40ae-91e9-6f622f29f129@osfda.org> Date: Sat, 30 May 2026 06:03:00 -0400 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Content-Language: en-US To: pgsql-pkg-debian@lists.postgresql.org From: "steve.b@osfda.org" Subject: Collation on Trexie/Debian 13... List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk This is a multi-part message in MIME format. --------------CfMHVazTjSFscsaVjStT5CD4 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit As you might have done like me, you upgraded a server to debian 13 and found that the _version_ of a collation you used to use in a database (PROBABLY "en_US.utf8", but possibly others...) no longer is supported on debian 13. And when you enter a database, you get an error and a hint suggesting you need to refresh the collation to a newer version. I made a */VERY/* simple script that walks the databases of a server and updates that collation in each one. I published it at this gitlab repo: https://gitlab.com/bitmodeler/pg-upgrade-collation You can shell to the postgres service account and run the script from there (AFTER YOU FIRST INSPECT IT!) You can either chmod +x the .sh file, or source it. You will also find notes there for a *recipe* for a more "industrial strength" script, should your needs require that... Respectfully, Steve Boriotti Senior Developer, full stack https://www.xing.com/profile/Steve_Boriotti --------------CfMHVazTjSFscsaVjStT5CD4 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

As you might have done like me, you upgraded a server to debian 13 and found that the _version_ of a collation you used to use in a database (PROBABLY "en_US.utf8", but possibly others...) no longer is supported on debian 13. And when you enter a database, you get an error and a hint suggesting you need to refresh the collation to a newer version.

I made a VERY simple script that walks the databases of a server and updates that collation in each one. I published it at this gitlab repo: https://gitlab.com/bitmodeler/pg-upgrade-collation

You can shell to the postgres service account and run the script from there (AFTER YOU FIRST INSPECT IT!) You can either chmod +x the .sh file, or source it.

You will also find notes there for a recipe for a more "industrial strength" script, should your needs require that...

Respectfully,
Steve Boriotti
Senior Developer, full stack
https://www.xing.com/profile/Steve_Boriotti


--------------CfMHVazTjSFscsaVjStT5CD4--