From: | Andreas Joseph Krogh <andreas(at)visena(dot)com> |
---|---|
To: | "Abraham, Danny" <danny_abraham(at)bmc(dot)com> |
Cc: | "pgsql-general(at)lists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org> |
Subject: | Sv: Base files compatibility between PG11 and PG15 |
Date: | 2023-08-17 10:10:11 |
Message-ID: | VisenaEmail.b48.50eaf865edbcab97.18a02f76c79@origo01.app.internal.visena.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
På torsdag 17. august 2023 kl. 11:32:47, skrev Abraham, Danny <
danny_abraham(at)bmc(dot)com <mailto:danny_abraham(at)bmc(dot)com>>:
Hi,
I have a database on Aurora(at)RDS(dot)
It Used V11.9, and then upgraded automatically by AWS to V15.2 AWS states that
it relies on compatibility provided by the PG community.
We now experience problems with the data.
Has anyone met similar issues? Compatibility of data files?
The data-files are nowhere near compatible between major-versions, as stated
clearly in all release notes:
https://www.postgresql.org/docs/release/12.0/
<https://www.postgresql.org/docs/release/12.0/>
https://www.postgresql.org/docs/release/13.0/
<https://www.postgresql.org/docs/release/13.0/>
https://www.postgresql.org/docs/release/14.0/
<https://www.postgresql.org/docs/release/14.0/>
https://www.postgresql.org/docs/release/15.0/
<https://www.postgresql.org/docs/release/15.0/>
They all state the same:
“A dump/restore using pg_dumpall or use of pg_upgrade or logical replication
is required for those wishing to migrate data from any previous release.”
--
Andreas Joseph Krogh
CTO / Partner - Visena AS
Mobile: +47 909 56 963
andreas(at)visena(dot)com <mailto:andreas(at)visena(dot)com>
www.visena.com <https://www.visena.com>
<https://www.visena.com>
From | Date | Subject | |
---|---|---|---|
Next Message | rob stone | 2023-08-17 12:57:15 | Re: Cast INTEGER to BIT confusion |
Previous Message | Abraham, Danny | 2023-08-17 09:32:47 | Base files compatibility between PG11 and PG15 |