| From: | Michael Banck <mbanck(at)gmx(dot)net> |
|---|---|
| To: | Achilleas Mantzios <a(dot)mantzios(at)cloud(dot)gatewaynet(dot)com> |
| Cc: | pgsql-admin(at)lists(dot)postgresql(dot)org |
| Subject: | Re: upgrade from 18beta1 to 18beta3 gives : FATAL: database files are incompatible with server |
| Date: | 2025-08-20 09:48:13 |
| Message-ID: | 68a599dd.050a0220.24b0ae.620b@mx.google.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Ron Johnson | 2025-08-20 10:43:55 | Re: PgBackrest directory access from another server |
| Previous Message | Achilleas Mantzios | 2025-08-20 09:25:08 | upgrade from 18beta1 to 18beta3 gives : FATAL: database files are incompatible with server |