Date: Thu, 24 Apr 2025 08:58:41 -0400
From: Bruce Momjian <bruce@momjian.us>
To: Greg Sabino Mullane <htamfids@gmail.com>
Cc: PostgreSQL-development <pgsql-hackers@lists.postgresql.org>
Subject: Re: pg_upgrade-breaking release
Message-ID: <aAo1gUT5mqMldUcn@momjian.us>
References: <aAoqiOt-R_eCiaSA@momjian.us>
 <CAKAnmmKTVP2E_0-SySVg-4rmjAY7T2Xs_eUgRRqqJTpWzuYE9g@mail.gmail.com>
 <aAowpA0MW34MDAKR@momjian.us>
 <CAKAnmmJPQgx8TfwdvCyZeN3LWfH3RMq_4r9b7hgq3RbCAgYKCg@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <CAKAnmmJPQgx8TfwdvCyZeN3LWfH3RMq_4r9b7hgq3RbCAgYKCg@mail.gmail.com>
Archived-At: <https://www.postgresql.org/message-id/aAo1gUT5mqMldUcn%40momjian.us>
Precedence: bulk

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.