Re: pg_upgrade-breaking release
| От | Greg Sabino Mullane |
|---|---|
| Тема | Re: pg_upgrade-breaking release |
| Дата | |
| Msg-id | CAKAnmmJPQgx8TfwdvCyZeN3LWfH3RMq_4r9b7hgq3RbCAgYKCg@mail.gmail.com обсуждение исходный текст |
| Ответ на | Re: pg_upgrade-breaking release (Bruce Momjian <bruce@momjian.us>) |
| Ответы |
Re: pg_upgrade-breaking release
|
| Список | pgsql-hackers |
On Thu, Apr 24, 2025 at 8:37 AM Bruce Momjian <bruce@momjian.us> wrote:
When I wrote pg_upgrade, I assumed at some point the value of changing the storage format would outweigh the value of allowing in-place upgrades. I guess that hasn't happened yet.
It reminds me of TDE, which is an good example of that, in a way. It requires pg_dump or logical replication to go from unencrypted -> encrypted. If core were to have something like that, I guess pg_upgrade could technically support it, but it would be equivalent to pg_dump. We've all been spoiled by that awesome --link option! :)
Cheers,
Greg
--
Crunchy Data - https://www.crunchydata.com
Enterprise Postgres Software Products & Tech Support
В списке pgsql-hackers по дате отправления: