Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1ss3zo-005ocu-Nb for pgsql-hackers@arkaria.postgresql.org; Sat, 21 Sep 2024 17:34:13 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1ss3zm-0073iC-CS for pgsql-hackers@arkaria.postgresql.org; Sat, 21 Sep 2024 17:34:11 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1ss3zm-0073i4-0Y for pgsql-hackers@lists.postgresql.org; Sat, 21 Sep 2024 17:34:11 +0000 Received: from mail-ej1-x635.google.com ([2a00:1450:4864:20::635]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1ss3zk-000M8X-Um for pgsql-hackers@lists.postgresql.org; Sat, 21 Sep 2024 17:34:10 +0000 Received: by mail-ej1-x635.google.com with SMTP id a640c23a62f3a-a8d51a7d6f5so428489466b.2 for ; Sat, 21 Sep 2024 10:34:08 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1726940047; x=1727544847; darn=lists.postgresql.org; h=to:date:message-id:subject:mime-version:from:from:to:cc:subject :date:message-id:reply-to; bh=mlfzMdyX2TDqUNhGEHZ49gEn2lzE4tdH8q+B9NadPAI=; b=cjRgltvCZDabACq7w1CKeEy6GqidwIqUO34f2khnhrp7djKvyN/7buiIipsn6kncTr Z2xI4xwVxSAolWebsrQDwTSejs+2bc5FKz8c/n7gNphGUaTvarVNfViZPANlm8kTwOxq Pjn+5SjjzxozK5iuZKFUfLZrJejAYLXiN5l5DYVdLMhHOkC2CPmqQveClgcwGtXTS2qZ ewwcdQgggJ8Sk8141wi7/UdbL4ymIRQ0I3Kfiz3CnSIoClfEVCOXSeOO639qpDl3/SkP XN49Guoc5y4o9RvzwQ4gWYl6poxbx1eMR9alCPnRap6GBFebILocfGmz/KuurR2ILiVD V8lg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1726940047; x=1727544847; h=to:date:message-id:subject:mime-version:from:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=mlfzMdyX2TDqUNhGEHZ49gEn2lzE4tdH8q+B9NadPAI=; b=MpqTLCJYZjzRqAyqjPA3OWCYf+D+oFJBBdKrmpWEd6MPw2ZZNBPJI7LybIsXb8rbZB p53eLvaXAUu2h1Oq6B24MKtRwCQrVOG6vFkEIqzjLsS+Z0tZTdROIjNxIEaelgRep26B PwoIHiqrV2owQFeyu/dvZKXm/BfUKVdSheawotZvTLqRCCa1GWOawYhY5Uhq4KvYO5NO wJ3VZ4+TcAIG4CZw/iJuBpVxA92BkesRZHzZp7WxMELdxj4Yg20qU5WWNShQLmqRLpxn nuYnG9WLz5NT4k1k36qVKdqCjU/Q/tb+J4zXSXUp6W7hIjEbfCXnXm9awK/yJr3Yau3X ouQQ== X-Gm-Message-State: AOJu0YyncQlP743P+B4rFMPrgLJmpBdoo53ga3p0Otvtreer/iibJfku Tg0V4ueG83cQUTuw/gwdFY+TFwxKoeDj5P8sCMZv5vCP3yNZh5Qcf0HJrQ== X-Google-Smtp-Source: AGHT+IEVIHc1eBPy5+UyBadYk70SbCJvClBnlsYIH91HyfTjFVRGbYpAMAya5kLAwBSfJOWYrVvoxw== X-Received: by 2002:a17:906:478f:b0:a8d:6712:2deb with SMTP id a640c23a62f3a-a90d5169170mr638345266b.61.1726940046840; Sat, 21 Sep 2024 10:34:06 -0700 (PDT) Received: from smtpclient.apple (ppp141237088007.access.hol.gr. [141.237.88.7]) by smtp.gmail.com with ESMTPSA id a640c23a62f3a-a9061330b08sm995807066b.201.2024.09.21.10.34.05 for (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Sat, 21 Sep 2024 10:34:06 -0700 (PDT) From: Florents Tselai Content-Type: multipart/alternative; boundary="Apple-Mail=_13E6E0D5-63BD-40AF-90B7-EFB8AC773A3D" Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3818.100.11.1.3\)) Subject: Docs pg_restore: Shouldn't there be a note about -n ? Message-Id: <284C4D55-4F90-4AA0-84C8-1E6A28DDF271@gmail.com> Date: Sat, 21 Sep 2024 20:33:53 +0300 To: pgsql-hackers X-Mailer: Apple Mail (2.3818.100.11.1.3) List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --Apple-Mail=_13E6E0D5-63BD-40AF-90B7-EFB8AC773A3D Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 I=E2=80=99m in the process of trying to restore some PG15/16 backups in = PG17. While playing with different -t and -n combinations I was browsing = through the docs. In pg_restore there are two notes about both -t / -n=20 > When -n / -t is specified, pg_dump makes no attempt to ... In pg_dump though there=E2=80=99s the equivalent note only for the -t = option. Shouldn=E2=80=99t it be a note as well for -n ?=20 Otherwise I would expect -n to cascade the restore to objects in other = schemas; Which I don=E2=80=99t think it does. Am I missing something?=20= --Apple-Mail=_13E6E0D5-63BD-40AF-90B7-EFB8AC773A3D Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=utf-8 I=E2=80=99m in = the process of trying to restore some PG15/16 backups in = PG17.

While playing with different -t and -n = combinations I was browsing through the = docs.

In pg_restore there are two notes = about both -t / -n 

> When = -n / -t is specified, pg_dump makes no attempt to = ...

In pg_dump though there=E2=80=99s the = equivalent note only for the -t = option.

Shouldn=E2=80=99t it be a note as well = for -n ? 

Otherwise I would expect -n to = cascade the restore to objects in other schemas;
Which I = don=E2=80=99t think it does.

Am I missing = something? 
= --Apple-Mail=_13E6E0D5-63BD-40AF-90B7-EFB8AC773A3D--