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.94.2) (envelope-from ) id 1tmVOU-007BEj-4K for pgsql-general@arkaria.postgresql.org; Mon, 24 Feb 2025 10:08:58 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1tmVOS-000UiQ-Vo for pgsql-general@arkaria.postgresql.org; Mon, 24 Feb 2025 10:08:56 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1tmVOS-000Ui9-KW for pgsql-general@lists.postgresql.org; Mon, 24 Feb 2025 10:08:56 +0000 Received: from mail-qv1-xf30.google.com ([2607:f8b0:4864:20::f30]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.96) (envelope-from ) id 1tmVOP-000SDw-2k for pgsql-general@lists.postgresql.org; Mon, 24 Feb 2025 10:08:55 +0000 Received: by mail-qv1-xf30.google.com with SMTP id 6a1803df08f44-6e6827984b2so50948786d6.1 for ; Mon, 24 Feb 2025 02:08:54 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=20230601; t=1740391734; x=1740996534; darn=lists.postgresql.org; h=to:subject:message-id:date:from:mime-version:from:to:cc:subject :date:message-id:reply-to; bh=BwRih1Abx+S6QgnbC0SiovfKfM7PJAA95Yi/2sDqoC8=; b=b+12jg1AwJJir9ndomPx+HXdcqp7kLbkIfxYt03a0SE2waszNRaG6JK0A0sxmdflLm /Su1gzuNH6Vj2aATquuILbUdX4caEM2E5wiCoxtVRhw2ZzgyL9HooRiRCcaggfvolUyp IeHHSP8zFHEgVI4qEOcrA2zwRFtgSNz07zAFjLO/RilW7Gi/v5gCN4aZVdR9pI1Tq155 X0Bm+2ZaDnX+AkOHUv+GEx2MRJj+E3lBa03gz3+tPi7aDBB/NLBnKc2NzfQPjBOQbubk G959Q61x9TJgIQNTYjkpy5zQLe4IBr9GYiZvl7fjhYBi05Oa9hSWXmiUNhj/XZ+Bmety asAg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1740391734; x=1740996534; h=to:subject:message-id:date:from:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=BwRih1Abx+S6QgnbC0SiovfKfM7PJAA95Yi/2sDqoC8=; b=BCrCG++JtsbG2+VGAWGxjLxVtvH0+iX4j6xM3h2HZZU25h2Rg+n/gNZ8XFTPTnjmnR 3ss5NfwfzkREGK7om0lK1JpkG3XLgSSDHgfz1slPMiNzrZUk1O7xKt2pwDDXeZNn+lLr fNfrc5pq15Xn6twDe07Sg1BYzkV8evgoFd1nxqwN6/D/4SSuFf5L89+iwyIAHF7/0R3L 0mGa4xM8/4hSol3ho2RBzl1Mq4NceGEH+icsWf+fyS6SYSV4x0W6UA7u+5TU1WOoP8hu Sy+9PH1POl39RoynU2t+gMwTeRIRn5R4xHyCKhAL+/6BCETFTTcZLBxglkwvkPfGR1Fv jBJA== X-Gm-Message-State: AOJu0Yy1aD3ldoDRbZ65rKa2mcdICghhjRuuImwkSuf3EI/QVJ6K0m9z C4cdkwaeRmoERq3PQjGEs6NqVTWmjTrGDTajQ2kU4hKp1RbHkGcFfz8HJv8sz74GNGgKpY5wdlu l5DtsykCXS/jquzCADuORc641ZHerePIU+DA= X-Gm-Gg: ASbGnctjmuzUgwjAwty3wo/7IfSIV8YuPGIO79saEjU/qK7e3BWa6+EecrlkirwX0Ww z8mGOA8lMYPiwQJf7CfJcLg/drCLfJujhF6TvUOn8OvugLdaR6KGjQIRa64TWI9ICZtPC9pYkCm WFwL4n1usW X-Google-Smtp-Source: AGHT+IGAoBlzQdogBDf2qW9vt9M276I5DLQvjkkbFocrNN9sBdNU8gAEmr5AuXCravkapaKwZne734dLPDCll5f5WdU= X-Received: by 2002:a05:6214:2264:b0:6d8:d79c:1cbd with SMTP id 6a1803df08f44-6e6ae7f6c7bmr141043076d6.15.1740391734171; Mon, 24 Feb 2025 02:08:54 -0800 (PST) MIME-Version: 1.0 From: Matthias Apitz Date: Mon, 24 Feb 2025 11:08:43 +0100 X-Gm-Features: AWEUYZkwhWK3k0KyNIblWvzG89jtIFXOwz6x7ObExiP0hZXtVwvW3FPhpWKi-CM Message-ID: Subject: COLLATION update in 13.1 To: pgsql-general@lists.postgresql.org Content-Type: multipart/alternative; boundary="00000000000015dfff062ee087cb" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --00000000000015dfff062ee087cb Content-Type: text/plain; charset="UTF-8" Hello, When the Linux OS is updated, for example from SLES 15 SP5 to SP6, the version of the glibc is sometimes updated, for example from 2.31 to 2.38. For existing databases this gives on SQL a warning as: user@rechner: $SC_SQL -Usisis sisis WARNING: database "sisis" has a collation version mismatch DETAIL: The database was created using collation version 2.31, but the operating system provides version 2.38. HINT: Rebuild all objects in this database that use the default collation and run ALTER DATABASE sisis REFRESH COLLATION VERSION, or build PostgreSQL with the right library version. ... This HINT works fine on 15.x and 16.x server versions. On 13.1 it gives an SQL ERROR: sisis=# ALTER DATABASE sisis REFRESH COLLATION VERSION; ERROR: syntax error at or near "REFRESH" LINE 1: ALTER DATABASE sisis REFRESH COLLATION VERSION; What is the procedure on 13.1 to bring the external (glibc) version in sync with. the used version in the PostgreSQL database? Thanks matthias --00000000000015dfff062ee087cb Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hello,

When the Linux OS is = updated, for example from SLES 15 SP5 to SP6, the version of the glibc is s= ometimes updated, for example from 2.31 to 2.38. For existing databases thi= s gives on SQL a warning as:

user@rechner: $SC_SQL -Usisis sisis
WARNING:  database "sisis" has a collation version mismatch
DETAIL:  The database was created using collation version 2.31, but the ope=
rating system provides version 2.38.
HINT:  Rebuild all objects in this database that use the default collation =
and run 
ALTER DATABASE sisis REFRESH COLLATION VERSION, or build Postgr= eSQL with the right library version. ...
This HINT works fine on 15.x and 16.x server versions.
On 13.1 it gives an SQL ERROR:

sisis=3D= # ALTER DATABASE sisis REFRESH COLLATION VERSION;
ERROR: =C2=A0syntax error at or near "REFRESH"
LINE 1: ALTER DATABASE sisis REFRESH COLLATION VERSION;

=

What is the procedure on 13.1 to bring the external (gl= ibc) version in sync with. the used version in the PostgreSQL database?


Thanks

matthias



=
--00000000000015dfff062ee087cb--