Re: pg_upgrade-breaking release - Mailing list pgsql-hackers

From Álvaro Herrera
Subject Re: pg_upgrade-breaking release
Date
Msg-id 202504241451.z7owyvvhaxbf@alvherre.pgsql
Whole thread Raw
In response to pg_upgrade-breaking release  (Bruce Momjian <bruce@momjian.us>)
Responses Re: pg_upgrade-breaking release
List pgsql-hackers
On 2025-Apr-24, Bruce Momjian wrote:

> Do we think most people are _not_ going to use pg_upgrade now that we
> are defaulting to checksums being enabled by default in PG 18?  And if
> so, do we think we are ever going to have a storage-format-changing
> release where pg_upgrade cannot be used?

Peter E posted a patch that allowed pg_upgrade to migrate (rewrite)
files from non-checksummed to checksummed, but he appears to have given
up on it for this release given an apparent lack of interest.
https://postgr.es/m/57957aca-3eae-4106-afb2-3008122b9950@eisentraut.org

-- 
Álvaro Herrera               48°01'N 7°57'E  —  https://www.EnterpriseDB.com/



pgsql-hackers by date:

Previous
From: "Vitaly Davydov"
Date:
Subject: Re: Slot's restart_lsn may point to removed WAL segment after hard restart unexpectedly
Next
From: Tom Lane
Date:
Subject: Re: What's our minimum supported Python version?