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: 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:56:13
Message-ID: eefe1947-4278-4f7c-a26c-8be6ccbd4b2b@wp.pl
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Christophe Pettus (20.11.2026 20:35):
> 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.

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.

Regards,
Eccenux

In response to

Responses

Browse pgsql-bugs by date

  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 Christophe Pettus 2026-11-20 19:35:39 Re: BUG #19927: PostgreSQL 16: SQL dump adds experimental/incompatible options like \restrict