From 2e4a84f6f546308dd82bf66ffd67621608cc05be Mon Sep 17 00:00:00 2001 From: Laurenz Albe Date: Tue, 30 Sep 2025 11:22:42 +0200 Subject: [PATCH v2] Document incompatible pg_restore options Most of the incumpatibilities (such as --file and --dbname) are pretty obvious and need no explanation. But it may not be obvious that --single-transaction cannot be used together with --create or multiple --jobs, so let's mention that in the documentation. Author: Ashutosh Bapat Reviewed-By: Laurenz Albe Discussion: https://postgr.es/m/CAExHW5ti5igDwOOde6shgfS7JPtCY9gNrkB3xNr%3DFuGTYVDSjQ%40mail.gmail.com --- doc/src/sgml/ref/pg_restore.sgml | 8 +++++++- 1 file changed, 7 insertions(+), 1 deletion(-) diff --git a/doc/src/sgml/ref/pg_restore.sgml b/doc/src/sgml/ref/pg_restore.sgml index a468a38361a..93b2f1659b3 100644 --- a/doc/src/sgml/ref/pg_restore.sgml +++ b/doc/src/sgml/ref/pg_restore.sgml @@ -160,6 +160,10 @@ PostgreSQL documentation CREATE DATABASE commands. All data is restored into the database name that appears in the archive. + + + This option cannot be used together with . + @@ -541,7 +545,9 @@ PostgreSQL documentation emitted commands in BEGIN/COMMIT). This ensures that either all the commands complete successfully, or no changes are applied. This option implies - . + . It cannot be used together with + , which switches database connections, or with + multiple . -- 2.51.0