Re: BUG #19927: PostgreSQL 16: SQL dump adds experimental/incompatible options like \restrict

From: Maciej Jaros <egil(at)wp(dot)pl>
To: Christophe Pettus <xof(at)thebuild(dot)com>
Cc: pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: BUG #19927: PostgreSQL 16: SQL dump adds experimental/incompatible options like \restrict
Date: 2026-11-20 23:31:42
Message-ID: 79cd25f9-0150-45bb-92da-eb1afce38d65@wp.pl
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Christophe Pettus (20.11.2026 21:17):
>>> There are also quite a few ways of upgrading PostgreSQL that don't involve dump files; you might investigate if any of those will meet your needs so that you aren't tied to dump file formats
>>
>> On Nov 20, 2026, at 11:56, Maciej Jaros <egil(at)wp(dot)pl> wrote:
>>
>> Well if the minor versions have breaking changes then how am I supposed to upgrade without making a backup? You seem to saying contradicting things.
> I'm not quite sure what you mean here.
>
> You don't need to do a dump/restore to upgrade from one minor version to another within a major version; you just restart on the newer binaries. I don't believe there's ever been a PostgreSQL minor version upgrade that required anything else (except possible post-upgrade maintenance activities like rebuilding certain indexes).

I'm not saying that a minor upgrade requires a dump/restore in theory.
I'm saying backup is required in practice, especially if PostgreSQL
doesn't follow semantic versioning best practices. And so I need a
backup and a rollback plan before upgrading a critical system with
thousands to millions of users. This takes hours, not minutes, and might
be put on hold for various reasons.

If minor versions can introduce breaking changes that aren't immediately
obvious, I also need to test the specific PostgreSQL version before
deploying it. This can take days or weeks or even more when waiting for
approval. Effectively, this makes the planning and testing effort for a
minor upgrade almost the same as for a major upgrade.

Regards,
Nux

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message surya poondla 2026-11-20 23:47:16 Re: Two issues with REFRESH MATERIALIZED VIEW CONCURRENTLY
Previous Message Zsolt Parragi 2026-11-20 22:59:32 Re: Timing issue in pg_basebackup