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

From: "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>
To: Maciej Jaros <egil(at)wp(dot)pl>
Cc: Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>, 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 22:29:45
Message-ID: CAKFQuwZuiAhTj_et2WA1wL9LncApVHR8rLCaaLN-pqpLbOh6hw@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Fri, Nov 20, 2026 at 12:23 PM Maciej Jaros <egil(at)wp(dot)pl> wrote:

> Does PostgreSQL follow semantic versioning principles?

Not strictly.

If so, shouldn't
> compatibility between minor releases be maintained?
>

This is why my answer was "not strictly"...

> Is there a recommended way to generate SQL dumps that remain compatible
> across minor releases of the same major version?
>
>
The data directory format is the invariant PostgreSQL worries about,
avoiding requiring pg_upgrade for a minor release. Everything else is
pretty much "unsupported" the moment a new minor release comes out.

We do in practice try to avoid annoying users but there is definitely a
line that doesn't get crossed. xml namespaces and pg_dump search path are
historical examples of willingly inflicted boundaries in this area. In
particular if the feature came about in response to a CVE like search_path
and this one.

David J.

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Jan Nidzwetzki 2026-11-20 22:33:35 Re: pg_rewind and hint bits leads to visibility corruption
Previous Message Michael Paquier 2026-11-20 22:18:38 Re: Segfaults in 18 and 19 when pgstats can't grow its DSA (back-patch of d9de60c5e4)