Content-Type: text/plain; charset="iso-8859-15"
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
From: "Daniel Verite" <daniel@manitou-mail.org>
Subject: Re: Help. The database was created using collation version 2.17, but
 the operating system provides version 2.34.
To: "Dmitry O Litvintsev" <litvinse@fnal.gov>
Cc: "pgsql-generallists.postgresql.org" <pgsql-general@lists.postgresql.org>
In-Reply-To: <SA1PR09MB7311E24901D1B718583739DFB9CA2@SA1PR09MB7311.namprd09.prod.outlook.com>
Date: Mon, 24 Jun 2024 10:48:34 +0200
Message-Id: <b8817ba6-1739-434f-bde5-5cb47ab85e8e@manitou-mail.org>
Archived-At: <https://www.postgresql.org/message-id/b8817ba6-1739-434f-bde5-5cb47ab85e8e%40manitou-mail.org>
Precedence: bulk

	Dmitry O Litvintsev wrote:

> Just want to make clear (sorry I am slow on uptake). I should first
> REINDEX and then ALTER DATABASE xxx REFRESH COLLATION VERSION, or
> first ALTER and then REINDEX or does the order of these action
> matter at all?

The order does not matter. The ALTER DATABASE command will simply
update the pg_database.datcollversion field with the current version
of libc. That will stop the warning being issued, but it doesn't have
any other concrete effect.

Best regards,
--=20
Daniel V=E9rit=E9
https://postgresql.verite.pro/
Twitter: @DanielVerite