| From: | Bruce Momjian <bruce(at)momjian(dot)us> |
|---|---|
| To: | Álvaro Herrera <alvherre(at)kurilemu(dot)de> |
| Cc: | PostgreSQL-development <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: pg_upgrade-breaking release |
| Date: | 2025-04-24 15:01:42 |
| Message-ID: | aApSVm7SmUd76WIc@momjian.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, Apr 24, 2025 at 04:51:08PM +0200, Álvaro Herrera wrote:
> 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
Yeah, I saw that, and I think we could do something similar for TDE if
we ever had it. I think we are suggesting people just do offline
addition of checksums rather than trying to do something fancy with
pg_upgrade.
--
Bruce Momjian <bruce(at)momjian(dot)us> https://momjian.us
EDB https://enterprisedb.com
Do not let urgent matters crowd out time for investment in the future.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Matheus Alcantara | 2025-04-24 15:18:28 | Re: extension_control_path and "directory" |
| Previous Message | Tom Lane | 2025-04-24 14:59:16 | Re: What's our minimum supported Python version? |