Re: pg_upgrade-breaking release
| От | Greg Sabino Mullane |
|---|---|
| Тема | Re: pg_upgrade-breaking release |
| Дата | |
| Msg-id | CAKAnmmKTVP2E_0-SySVg-4rmjAY7T2Xs_eUgRRqqJTpWzuYE9g@mail.gmail.com обсуждение исходный текст |
| Ответ на | pg_upgrade-breaking release (Bruce Momjian <bruce@momjian.us>) |
| Ответы |
Re: pg_upgrade-breaking release
|
| Список | pgsql-hackers |
On Thu, Apr 24, 2025 at 8:12 AM Bruce Momjian <bruce@momjian.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
В списке pgsql-hackers по дате отправления: