Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1kgWLb-0007GC-0D for pgsql-bugs@arkaria.postgresql.org; Sat, 21 Nov 2020 17:06:51 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1kgWLY-0004yN-Ps for pgsql-bugs@arkaria.postgresql.org; Sat, 21 Nov 2020 17:06:48 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1kgWLY-0004yF-JL for pgsql-bugs@lists.postgresql.org; Sat, 21 Nov 2020 17:06:48 +0000 Received: from wout1-smtp.messagingengine.com ([64.147.123.24]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1kgWLV-0003RR-NM for pgsql-bugs@lists.postgresql.org; Sat, 21 Nov 2020 17:06:48 +0000 Received: from compute2.internal (compute2.nyi.internal [10.202.2.42]) by mailout.west.internal (Postfix) with ESMTP id 0C0ACE0C; Sat, 21 Nov 2020 12:06:41 -0500 (EST) Received: from mailfrontend1 ([10.202.2.162]) by compute2.internal (MEProxy); Sat, 21 Nov 2020 12:06:42 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-type:date:from:in-reply-to :message-id:mime-version:subject:to:x-me-proxy:x-me-proxy :x-me-sender:x-me-sender:x-sasl-enc; s=fm1; bh=36KvGa6ihDR/rD/ht bLoREHYc8xYZNzsE1IoWZXBxiE=; b=Yl4nrzRiWN9TV02NfC8qnSol/mhvh9ot1 7L+Ac5AUiwMpiMM/8Cohw6oUqNzoHzqnJqfg8XalmeDz3RBK/yPXQfuZ8kYSAnGL NU37ypGrvlFVDpDzE1YG5EcwT5am0A1oIcIyt/mMz4UXwZsCoxIt1crzwqg0WrBY Ano8bXlJ2CcGNQJJ2ZbzKY2QQu7nPGxXlXnjLr96R9Zh7pDOyz8Hg6sNtW2E0aor xa/E6mJQlk1I9SaMYqS5zesAgpT5mIpQEPn0WKnaSp33xZjT27LRvZ4LKEGs/GNg Zdw2cug0as+ISetfwJgl5k2ON3c1Vn6zrAR7Iak7oxHtZ0Ee7MZ+Q== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedujedrudegvddgleekucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhepfffhvffukfggtggujggfsehttdertddtredvnecuhfhrohhmpeetlhhvrghr ohcujfgvrhhrvghrrgcuoegrlhhvhhgvrhhrvgesrghlvhhhrdhnohdqihhprdhorhhgqe enucggtffrrghtthgvrhhnpeevgfelveegueejgefhgeetgefhgeehieefheehleetteei udeiiefhgffgheffteenucfkphepudeltddrleehrddukedrjeelnecuvehluhhsthgvrh fuihiivgeptdenucfrrghrrghmpehmrghilhhfrhhomheprghlvhhhvghrrhgvsegrlhhv hhdrnhhoqdhiphdrohhrgh X-ME-Proxy: Received: from perhan.alvh.no-ip.org (unknown [190.95.18.79]) by mail.messagingengine.com (Postfix) with ESMTPA id 1857E328005E; Sat, 21 Nov 2020 12:06:41 -0500 (EST) Received: by perhan.alvh.no-ip.org (Postfix, from userid 1000) id 482472A621F; Sat, 21 Nov 2020 14:06:38 -0300 (-03) Date: Sat, 21 Nov 2020 14:06:38 -0300 From: Alvaro Herrera To: Zsolt Ero Cc: Tom Lane , "David G. Johnston" , PostgreSQL mailing lists Subject: Re: BUG #16732: pg_dump creates broken backups Message-ID: <20201121170638.GA10288@alvherre.pgsql> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.10.1 (2018-07-13) List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk On 2020-Nov-21, Zsolt Ero wrote: > I didn't state why I'm doing all this: basically all I'd like to do is > exclude a table when restoring data. > The only way I managed to do this was to grep -v the list file before data > only restore. Why do you do that? It seems much easier to produce a complete dump, then obtain the --list from it, do "grep -v" of the TABLE DATA element for that table, then give that file to pg_restore. It would restore everything in the right order, including that table's definition, but excluding that table's data.