Message-ID: <ae62cc30-2374-4154-ae54-2e40f2b1f4cc@cloud.gatewaynet.com>
Date: Wed, 20 Aug 2025 11:54:59 +0100
MIME-Version: 1.0
Subject: Re: upgrade from 18beta1 to 18beta3 gives : FATAL: database files are
 incompatible with server
To: Michael Banck <mbanck@gmx.net>
Cc: pgsql-admin@lists.postgresql.org
References: <09634814-40b4-4096-b48e-3ccffb64f872@cloud.gatewaynet.com>
 <68a599dd.050a0220.24b0ae.620b@mx.google.com>
Content-Language: en-US
From: Achilleas Mantzios <a.mantzios@cloud.gatewaynet.com>
In-Reply-To: <68a599dd.050a0220.24b0ae.620b@mx.google.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: 
 <https://www.postgresql.org/message-id/ae62cc30-2374-4154-ae54-2e40f2b1f4cc%40cloud.gatewaynet.com>
Precedence: bulk

On 8/20/25 10:48, Michael Banck wrote:

> Hi,
>
> On Wed, Aug 20, 2025 at 10:25:08AM +0100, Achilleas Mantzios wrote:
>> 12:12:43.679 EEST  @ line:1 FATAL:  database files are incompatible with
>> server
>> [15615] 68a5918b.3cff 2025-08-20 12:12:43.679 EEST  @ line:2 DETAIL:  The
>> database cluster was initialized with CATALOG_VERSION_NO 202504091, but the
>> server was compiled with CATALOG_VERSION_NO 20250629
>> 1.
>> [15615] 68a5918b.3cff 2025-08-20 12:12:43.679 EEST  @ line:3 HINT:  It looks
>> like you need to initdb.
>>
>> Is the catalog version indeed different between 18beta1 and 18beta3 ?
> Yes, that is correct, you will need to do a migration. Postgres only
> guarantees catalog stability after the first stable release (but usually
> at least the release candidates no longer change the catalog).
ok, thanks, makes sense.
>
> Michael