| From: | Álvaro Herrera <alvherre(at)kurilemu(dot)de> |
|---|---|
| To: | Bruce Momjian <bruce(at)momjian(dot)us> |
| Cc: | PostgreSQL-development <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: pg_upgrade-breaking release |
| Date: | 2025-04-24 14:51:08 |
| Message-ID: | 202504241451.z7owyvvhaxbf@alvherre.pgsql |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2025-04-24 14:59:16 | Re: What's our minimum supported Python version? |
| Previous Message | Vitaly Davydov | 2025-04-24 14:32:39 | Re: Slot's restart_lsn may point to removed WAL segment after hard restart unexpectedly |