| 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:51:41 |
| Message-ID: | CAKAnmmJPQgx8TfwdvCyZeN3LWfH3RMq_4r9b7hgq3RbCAgYKCg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, Apr 24, 2025 at 8:37 AM Bruce Momjian <bruce(at)momjian(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2025-04-24 12:58:41 | Re: pg_upgrade-breaking release |
| Previous Message | torikoshia | 2025-04-24 12:48:57 | Re: RFC: Logging plan of the running query |