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

From Bruce Momjian
Subject Re: pg_upgrade-breaking release
Date
Msg-id aAo1gUT5mqMldUcn@momjian.us
Whole thread Raw
In response to Re: pg_upgrade-breaking release  (Greg Sabino Mullane <htamfids@gmail.com>)
List pgsql-hackers
On Thu, Apr 24, 2025 at 08:51:41AM -0400, Greg Sabino Mullane wrote:
> 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! :) 

True on spoiled, but I think TDE is being held back by code complexity,
not upgrade complexity.

-- 
  Bruce Momjian  <bruce@momjian.us>        https://momjian.us
  EDB                                      https://enterprisedb.com

  Do not let urgent matters crowd out time for investment in the future.



pgsql-hackers by date:

Previous
From: Greg Sabino Mullane
Date:
Subject: Re: pg_upgrade-breaking release
Next
From: Andrei Lepikhov
Date:
Subject: Re: MergeAppend could consider sorting cheapest child path