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

From: Maciej Jaros <egil(at)wp(dot)pl>
To: 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 18:41:32
Message-ID: 6c5ae569-7522-4d8a-a0b5-e4330226fb5f@wp.pl
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

What I'm asking for is a way to generate reasonably portable SQL dumps
that aren't tied to a specific minor version.

My understanding is that minor releases should not introduce breaking
changes. In practice, if an upgrade introduces such changes across
multiple environments, it is simply impossible to upgrade quickly. We
have gigabytes of data on each server and more than 20 servers. Some of
them are test servers with different upgrade schedules and processes.
Also in the past we already seen breaking changes so since then we tend
to test each version for days or weeks.

Does PostgreSQL follow semantic versioning principles? If so, shouldn't
compatibility between minor releases be maintained?

Is there a recommended way to generate SQL dumps that remain compatible
across minor releases of the same major version?

Regards,
Maciej "Nux" Jaros

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Tom Lane 2026-11-20 19:16:50 Re: BUG #19923: SEARCH/CYCLE with DISTINCT in the recursive term: rows depend on input order
Previous Message Tom Lane 2026-11-20 18:17:17 Re: BUG #19923: SEARCH/CYCLE with DISTINCT in the recursive term: rows depend on input order