public inbox for [email protected]
help / color / mirror / Atom feedupgrade from 18beta1 to 18beta3 gives : FATAL: database files are incompatible with server
3+ messages / 2 participants
[nested] [flat]
* upgrade from 18beta1 to 18beta3 gives : FATAL: database files are incompatible with server
@ 2025-08-20 09:25 Achilleas Mantzios <[email protected]>
2025-08-20 09:48 ` Re: upgrade from 18beta1 to 18beta3 gives : FATAL: database files are incompatible with server Michael Banck <[email protected]>
0 siblings, 1 reply; 3+ messages in thread
From: Achilleas Mantzios @ 2025-08-20 09:25 UTC (permalink / raw)
To: [email protected]
Hi for the sake of answering here :
https://www.postgresql.org/message-id/48a32f45-57f2-4560-ae94-3488b3568c8a%40cloud.gatewaynet.com
(although I didn't find anything indicating any hope for any change
regarding my deadlock), it seems I am unable to binary upgrade from
18beta1 to 18beta3 the traditional easy way between minor releases.
After : make install , it gives
postgres@smadevnu:~ % pg_ctl -D data restart
waiting for server to shut down...... done
server stopped
waiting for server to start.... [15615] 68a5918b.3cff 2025-08-20
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.
[15615] 68a5918b.3cff 2025-08-20 12:12:43.679 EEST @ line:4 LOG:
database system is shut down
stopped waiting
pg_ctl: could not start server
Examine the log output.
Is the catalog version indeed different between 18beta1 and 18beta3 ?
^ permalink raw reply [nested|flat] 3+ messages in thread
* Re: upgrade from 18beta1 to 18beta3 gives : FATAL: database files are incompatible with server
2025-08-20 09:25 upgrade from 18beta1 to 18beta3 gives : FATAL: database files are incompatible with server Achilleas Mantzios <[email protected]>
@ 2025-08-20 09:48 ` Michael Banck <[email protected]>
2025-08-20 10:54 ` Re: upgrade from 18beta1 to 18beta3 gives : FATAL: database files are incompatible with server Achilleas Mantzios <[email protected]>
0 siblings, 1 reply; 3+ messages in thread
From: Michael Banck @ 2025-08-20 09:48 UTC (permalink / raw)
To: Achilleas Mantzios <[email protected]>; +Cc: [email protected]
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).
Michael
^ permalink raw reply [nested|flat] 3+ messages in thread
* Re: upgrade from 18beta1 to 18beta3 gives : FATAL: database files are incompatible with server
2025-08-20 09:25 upgrade from 18beta1 to 18beta3 gives : FATAL: database files are incompatible with server Achilleas Mantzios <[email protected]>
2025-08-20 09:48 ` Re: upgrade from 18beta1 to 18beta3 gives : FATAL: database files are incompatible with server Michael Banck <[email protected]>
@ 2025-08-20 10:54 ` Achilleas Mantzios <[email protected]>
0 siblings, 0 replies; 3+ messages in thread
From: Achilleas Mantzios @ 2025-08-20 10:54 UTC (permalink / raw)
To: Michael Banck <[email protected]>; +Cc: [email protected]
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
^ permalink raw reply [nested|flat] 3+ messages in thread
end of thread, other threads:[~2025-08-20 10:54 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2025-08-20 09:25 upgrade from 18beta1 to 18beta3 gives : FATAL: database files are incompatible with server Achilleas Mantzios <[email protected]>
2025-08-20 09:48 ` Michael Banck <[email protected]>
2025-08-20 10:54 ` Achilleas Mantzios <[email protected]>
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox