Re: Help. The database was created using collation version 2.17, but the operating system provides version 2.34.

From: "Daniel Verite" <daniel(at)manitou-mail(dot)org>
To: "Dmitry O Litvintsev" <litvinse(at)fnal(dot)gov>
Cc: "pgsql-generallists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org>
Subject: Re: Help. The database was created using collation version 2.17, but the operating system provides version 2.34.
Date: 2024-06-24 08:48:34
Message-ID: b8817ba6-1739-434f-bde5-5cb47ab85e8e@manitou-mail.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

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,
--
Daniel Vérité
https://postgresql.verite.pro/
Twitter: @DanielVerite

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message arun chirappurath 2024-06-24 10:29:01 Execute permission to function
Previous Message Laurenz Albe 2024-06-24 08:23:06 Re: Upgrade PG from 12 to latest