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

From Bruce Momjian
Subject Re: pg_upgrade-breaking release
Date
Msg-id aAowpA0MW34MDAKR@momjian.us
Whole thread Raw
In response to Re: pg_upgrade-breaking release  (Greg Sabino Mullane <htamfids@gmail.com>)
Responses Re: pg_upgrade-breaking release
Re: pg_upgrade-breaking release
List pgsql-hackers
On Thu, Apr 24, 2025 at 08:35:10AM -0400, Greg Sabino Mullane wrote:
> On Thu, Apr 24, 2025 at 8:12 AM Bruce Momjian <bruce@momjian.us> wrote:
> 
>     Do we think most people are _not_ going to use pg_upgrade now that we
>     are defaulting to checksums being enabled by default in PG 18?
> 
> 
> I cannot imagine this would stop anyone from upgrading. It's one additional
> flag, which was already a requirement for those going the other direction in
> the past (checksums -> no checksums). And I also assume that "most people" are
> already running with checksums enabled.
> 
> 
>       And if so, do we think we are ever going to have a
>     storage-format-changing release where pg_upgrade cannot be used?
> 
> 
> Seems very unlikely, that would kind of go against the whole purpose of
> pg_upgrade.

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.

-- 
  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: "Zhijie Hou (Fujitsu)"
Date:
Subject: RE: Conflict detection for update_deleted in logical replication