| From: | Greg Sabino Mullane <htamfids(at)gmail(dot)com> |
|---|---|
| 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 12:35:10 |
| Message-ID: | CAKAnmmKTVP2E_0-SySVg-4rmjAY7T2Xs_eUgRRqqJTpWzuYE9g@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, Apr 24, 2025 at 8:12 AM Bruce Momjian <bruce(at)momjian(dot)us> 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?
I cannot imagine this would stop anyone from upgrading. It's one additional
flag, which was already a requirement for those going the other direction
in the past (checksums -> no checksums). And I also assume that "most
people" are already running with checksums enabled.
And if so, do we think we are ever going to have a
> storage-format-changing release where pg_upgrade cannot be used?
>
Seems very unlikely, that would kind of go against the whole purpose of
pg_upgrade.
--
Cheers,
Greg
--
Crunchy Data - https://www.crunchydata.com
Enterprise Postgres Software Products & Tech Support
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2025-04-24 12:37:56 | Re: pg_upgrade-breaking release |
| Previous Message | Amit Kapila | 2025-04-24 12:30:07 | Re: POC: enable logical decoding when wal_level = 'replica' without a server restart |