Re: PoC: true in-place major version upgrades

From: Nathan Bossart <nathandbossart(at)gmail(dot)com>
To: John Naylor <johncnaylorls(at)gmail(dot)com>
Cc: Robert Haas <robertmhaas(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: PoC: true in-place major version upgrades
Date: 2026-11-02 14:14:34
Message-ID: auiayn5vFcRUvuun@nathan
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, Nov 02, 2026 at 07:57:02PM +0700, John Naylor wrote:
> On Fri, Oct 30, 2026 at 2:00 AM Nathan Bossart <nathandbossart(at)gmail(dot)com> wrote:
>> it's just software and almost anything is possible, but in this case I
>> suspect it comes with a huge amount of complexity, ongoing maintenance
>> burden, and really weird trade-offs.
>
> And yet, many DBMS's are able to do it, so any theory about how
> impossibly hard it is has to explain that fact.

As Tom alluded upthread, I think the main factor is that we (a relatively
small group of committers) have thus far been unwilling to take on the
maintenance cost and/or the restrictions on catalog changes that come with
it. I suspect this project becomes a whole lot more feasible if we can
find a way to minimize those.

> It should be table stakes for a DBMS that aspires to be enterprise-grade.

Agreed. I think many, many users would be happy to have this feature.

--
nathan

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Guillaume Lelarge 2026-11-02 14:20:27 Re: Setting the number of digits after the decimal point with a psql's pset variable
Previous Message Robert Haas 2026-11-02 14:10:08 Re: PoC: true in-place major version upgrades