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 1vmqNe-00Gvo7-1l for pgsql-docs@arkaria.postgresql.org; Mon, 02 Feb 2026 09:38:02 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.96) (envelope-from ) id 1vmqNc-00DGPM-2E for pgsql-docs@arkaria.postgresql.org; Mon, 02 Feb 2026 09:38:01 +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 1vmpui-00D3rp-08 for pgsql-docs@lists.postgresql.org; Mon, 02 Feb 2026 09:08:09 +0000 Received: from mahout.postgresql.org ([2001:4800:3e1:1::227]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.98.2) (envelope-from ) id 1vmpuf-00000000eFv-2XbU for pgsql-docs@lists.postgresql.org; Mon, 02 Feb 2026 09:08:08 +0000 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=postgresql.org; s=20171124; h=Message-ID:Date:Reply-To:Cc:From:To:Subject: Content-Transfer-Encoding:MIME-Version:Content-Type:Sender:Content-ID: Content-Description:In-Reply-To:References; bh=ilc/vSHZNtMNKTzseuUNIj8NqziCoLVHIvP5MAEQIWk=; b=TKv8DQV1hwuNgGvM8sj3gSYEdM Vq8DwnkX2ZWdjgbEZzTDjRdml7PQ3dbKLmUPxb4jyaB+zcbWRs/r1RGIFWMfN4wLbP/vaIoKaGXju vxMxW6pV0hL4ZNxNvqU+yIiDHwZf5nyZ8prbjq8zn9H09JiWrTTXAEUBjewwfGftTUjvW/+CifhX6 pIDDXEK76DAPA9xcFdNE5K9pMCJDW83kDre5cgbJ0alnTZf/nGBm/EKeygaKLw0EiIxnlBWWoMVQT PgYgjBfvFc10mzFrMiIM7oqz8GJ9cxYtsAjIPSrlEb/eDh7Ol5FZA+mOrS4uhRKtj/H+1PeRvpbpz GJTYvmlQ==; Received: from wrigleys.postgresql.org ([2a02:16a8:dc51::60]) by mahout.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1vmpue-001qBE-03 for pgsql-docs@lists.postgresql.org; Mon, 02 Feb 2026 09:08:04 +0000 Received: from localhost ([127.0.0.1] helo=wrigleys.postgresql.org) by wrigleys.postgresql.org with esmtp (Exim 4.96) (envelope-from ) id 1vmpuc-003FcV-0c for pgsql-docs@lists.postgresql.org; Mon, 02 Feb 2026 09:08:03 +0000 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Subject: OS system version upgrade (glibc / libicu version change) To: pgsql-docs@lists.postgresql.org From: PG Doc comments form Cc: alexey.shishkin@enterprisedb.com Reply-To: alexey.shishkin@enterprisedb.com, pgsql-docs@lists.postgresql.org Date: Mon, 02 Feb 2026 09:07:41 +0000 Message-ID: <177002326159.803.1983703962002247846@wrigleys.postgresql.org> X-Auto-Response-Suppress: All Auto-Submitted: auto-generated List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk The following documentation comment has been logged on the website: Page: https://www.postgresql.org/docs/18/collation.html Description: Hi, Team ! It looks like the PostgreSQL documentation doesn't explain the customers what to do with PostgreSQL in case of OS system version upgrade or/and glibc / libicu version change. There're many links/blogs available where the required actions are explained. https://knowledge.enterprisedb.com/hc/en-us/articles/13520015051420-glibc-l= ocale-data-changes https://www.crunchydata.com/blog/postgres-migration-pitstop-collations https://wiki.postgresql.org/wiki/Locale_data_changes The thing is some of the recommendations are not complete or/and not up-to-date. I see a lot of confusion in the field about this topic, because PostgreSQL users don't have the 'official recommendations' from the PostgreSQL community. So, my proposal to dedicate a chapter in the PostgreSQL documentation about the topic. best regards Alexey Shishkin