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 1twaoO-00Fq7I-CJ for pgsql-general@arkaria.postgresql.org; Mon, 24 Mar 2025 05:57:24 +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 1twaoM-00DinB-GW for pgsql-general@arkaria.postgresql.org; Mon, 24 Mar 2025 05:57:22 +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.94.2) (envelope-from ) id 1twaoM-00Din3-52 for pgsql-general@lists.postgresql.org; Mon, 24 Mar 2025 05:57:22 +0000 Received: from ms-10.1blu.de ([178.254.4.101]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1twaoJ-000o2m-2f for pgsql-general@lists.postgresql.org; Mon, 24 Mar 2025 05:57:21 +0000 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=unixarea.de ; s=blu3434000; h=In-Reply-To:Content-Transfer-Encoding:Content-Type: MIME-Version:References:Reply-To:Message-ID:Subject:Cc:To:From:Date:Sender: Content-ID:Content-Description; bh=/mx5FFLaOXil9bak77D5L60MX6gJyM2GxqYtwXv1KTw=; b=kArnJ5ShnZJma7JfXBrTg7EBml wVyz0Ps5oIYCcsjVoyQ+0JwJYw9M6YN9i9l1U2MkcJc68nGHLx8UJeHt0QTalqlEYoUCbX07v453C fhXku3TaQ9jQCXOWFWw3gyol6u4k3IRimvfO4qX0kAAJQUWini7psc6QENtF4VbwoKQpR/beOR8Fw tP4tLSwyRRPsorK2SRJn9yl0JILQzj+nGLCKbMdHiMLU03neeFyekXfJcPBBKknrz797fv267XPIX 6OGtzewVDtUIuzIklDCfhdTBK8ASEsl1aye5sCnSOl7+P1NbbQSCt2YELha3qudEX8gxhZszvuyto 3MF9MMgw==; Received: from [62.216.210.181] (helo=localhost.unixarea.de) by ms-10.1blu.de with esmtpsa (TLS1.2) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.95) (envelope-from ) id 1twaoH-00C668-Uk; Mon, 24 Mar 2025 06:57:18 +0100 Received: from localhost.my.domain (c720-1400094 [127.0.0.1]) by localhost.unixarea.de (8.17.1/8.14.9) with ESMTP id 52O5vIiT001381; Mon, 24 Mar 2025 06:57:18 +0100 (CET) (envelope-from guru@unixarea.de) Received: (from guru@localhost) by localhost.my.domain (8.17.1/8.14.9/Submit) id 52O5vILi001380; Mon, 24 Mar 2025 06:57:18 +0100 (CET) (envelope-from guru@unixarea.de) X-Authentication-Warning: localhost.my.domain: guru set sender to guru@unixarea.de using -f Date: Mon, 24 Mar 2025 06:57:18 +0100 From: Matthias Apitz To: Laurenz Albe Cc: pgsql-general@lists.postgresql.org Subject: Re: COLLATION update in 13.1 Message-ID: Reply-To: Matthias Apitz References: <20250224023225.197cac12@ardentperf.com> <6118973a513658c4a46d9399f3691d0ef21672e8.camel@cybertec.at> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <6118973a513658c4a46d9399f3691d0ef21672e8.camel@cybertec.at> X-Operating-System: FreeBSD 14.0-CURRENT r1400094 (amd64) X-message-flag: Mails in HTML will not be read! Please, only plain text. X-Con-Id: 51246 X-Con-U: 0-guru X-Originating-IP: 62.216.210.181 List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk El día lunes, febrero 24, 2025 a las 12:41:05p. m. +0100, Laurenz Albe escribió: > Perhaps I need not say that, but ALTER COLLATION ... REFRESH VERSION only > makes the warning disappear. > > If you want to avoid data corruption, rebuild all indexes on strings, > then make the warning disappear. > > Yours, > Laurenz Albe One last question related to ALTER COLLATION ... In our clusters are also the databases 'postgres', 'template0' and 'template1'. The latter we never us and we CREATE new databases from 'template0'. Anyway, does it make sense to ALTER COLLATION in these databases as well? Thanks matthias -- Matthias Apitz, ✉ guru@unixarea.de, http://www.unixarea.de/ +49-176-38902045 Public GnuPG key: http://www.unixarea.de/key.pub Annalena Baerbock: "We are fighting a war against Russia ..." (25.1.2023) I, Matthias, I am not at war with Russia. Я не воюю с Россией. Ich bin nicht im Krieg mit Russland.