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

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Christophe Pettus <xof(at)thebuild(dot)com>
Cc: Maciej Jaros <egil(at)wp(dot)pl>, 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:17
Message-ID: 1701944.1795204577@sss.pgh.pa.us
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Christophe Pettus <xof(at)thebuild(dot)com> writes:
> This is a relatively unusual situation. You can automate removal of the \restrict using sed or equivalent if you need a hands-free solution.

You can also simply ignore these error messages, though I grant that
feels dangerous. There have been many cases in the past where
cross-version dump restoration would result in harmless error messages.

regards, tom lane

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Christophe Pettus 2026-11-20 20:17:34 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