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 1uof4D-007ih4-Ba for pgsql-admin@arkaria.postgresql.org; Wed, 20 Aug 2025 09:25:14 +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 1uof4C-006mz9-OO for pgsql-admin@arkaria.postgresql.org; Wed, 20 Aug 2025 09:25:13 +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 1uof4C-006mxj-DY for pgsql-admin@lists.postgresql.org; Wed, 20 Aug 2025 09:25:13 +0000 Received: from cloud.gatewaynet.com ([185.90.37.94]) by magus.postgresql.org with esmtps (TLS1.2) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1uof4A-000ski-22 for pgsql-admin@lists.postgresql.org; Wed, 20 Aug 2025 09:25:12 +0000 Content-Type: multipart/alternative; boundary="------------SuEHoeVfE0wmk7yadyUUB80w" Message-ID: <09634814-40b4-4096-b48e-3ccffb64f872@cloud.gatewaynet.com> Date: Wed, 20 Aug 2025 10:25:08 +0100 MIME-Version: 1.0 Content-Language: en-US To: pgsql-admin@lists.postgresql.org From: Achilleas Mantzios Subject: upgrade from 18beta1 to 18beta3 gives : FATAL: database files are incompatible with server List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk This is a multi-part message in MIME format. --------------SuEHoeVfE0wmk7yadyUUB80w Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit 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 ? --------------SuEHoeVfE0wmk7yadyUUB80w Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 8bit

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 ?

--------------SuEHoeVfE0wmk7yadyUUB80w--