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

From: PG Bug reporting form <noreply(at)postgresql(dot)org>
To: pgsql-bugs(at)lists(dot)postgresql(dot)org
Cc: egil(at)wp(dot)pl
Subject: BUG #19927: PostgreSQL 16: SQL dump adds experimental/incompatible options like \restrict
Date: 2026-11-20 13:21:09
Message-ID: 19927-f9d9af68b2d6d3ce@postgresql.org
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

The following bug has been logged on the website:

Bug reference: 19927
Logged by: Maciej Nux
Email address: egil(at)wp(dot)pl
PostgreSQL version: 16.15
Operating system: Ubuntu
Description:

Hi. I encountered a compatibility issue while restoring a plain SQL dump
using PostgreSQL 16.

Created sql dump on one machine with 16.15 and wanted to restore on test
machine that happens to be on 16.3 at the moment.

**Expected:**

A plain SQL dump generated using PostgreSQL 16 tools should be restorable
using compatible PostgreSQL 16 client tools without encountering unsupported
psql meta-commands.

**Actual:**

The restore process encounters `\restrict`, which PostgreSQL 16.3 `psql`
does not recognise, and terminates with a non-zero exit code.

**Workarounds?**

If there is a workaround I would be interested. For procedural reasons we
cannot upgrade all servers at once, but also might need to move clients
around.

1. Is there any supported option to prevent `\restrict` and `\unrestrict`
from appearing in plain SQL dumps?
2. What is the recommended way to ensure compatibility when generating and
restoring plain SQL dumps?

Thanks in advance for any guidance.

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message ZizhuanLiu X-MAN 2026-11-20 14:22:33 Re: BUG #17545: Incorrect selectivity for IS NOT DISTINCT FROM and NULLs
Previous Message PG Bug reporting form 2026-11-20 13:13:19 BUG #19926: Incorrect join selectivity for <> with NULLs (related to BUG #17545)