Re: pg_upgrade-breaking release - Mailing list pgsql-hackers

From Greg Sabino Mullane
Subject Re: pg_upgrade-breaking release
Date
Msg-id CAKAnmmJPQgx8TfwdvCyZeN3LWfH3RMq_4r9b7hgq3RbCAgYKCg@mail.gmail.com
Whole thread Raw
In response to Re: pg_upgrade-breaking release  (Bruce Momjian <bruce@momjian.us>)
Responses Re: pg_upgrade-breaking release
List 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

--
Enterprise Postgres Software Products & Tech Support

pgsql-hackers by date:

Previous
From: torikoshia
Date:
Subject: Re: RFC: Logging plan of the running query
Next
From: Bruce Momjian
Date:
Subject: Re: pg_upgrade-breaking release