| From: | Christophe Pettus <xof(at)thebuild(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 19:35:39 |
| Message-ID: | 8ABC4147-AAF9-40A5-BBC1-802F60B49567@thebuild.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
> On Nov 20, 2026, at 10:41, Maciej Jaros <egil(at)wp(dot)pl> wrote:
> Does PostgreSQL follow semantic versioning principles? If so, shouldn't compatibility between minor releases be maintained?
Tom Lane answered the question previously on this thread:
> On Nov 20, 2026, at 07:25, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>
> This was installed as part of a security fix. We will not be
> removing it.
>
> (It is generally true that we try not to break backwards compatibility
> of dump files. But there are exceptions, and this was one.)
This is a relatively unusual situation. You can automate removal of the \restrict using sed or equivalent if you need a hands-free solution.
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.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2026-11-20 19:56:17 | Re: BUG #19927: PostgreSQL 16: SQL dump adds experimental/incompatible options like \restrict |
| Previous 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 |