Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1YoYLv-0006Uw-V8 for pgsql-general@arkaria.postgresql.org; Sat, 02 May 2015 14:25:12 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.80) (envelope-from ) id 1YoYLv-0005vL-FR for pgsql-general@arkaria.postgresql.org; Sat, 02 May 2015 14:25:11 +0000 Received: from makus.postgresql.org ([2001:4800:1501:1::229]) by malur.postgresql.org with esmtps (TLS1.2:RSA_AES_256_CBC_SHA256:256) (Exim 4.80) (envelope-from ) id 1YoYLu-0005uU-5K for pgsql-general@postgresql.org; Sat, 02 May 2015 14:25:10 +0000 Received: from mailout01.ims-firmen.de ([213.174.32.96]) by makus.postgresql.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.84) (envelope-from ) id 1YoYLq-0003e6-OL for pgsql-general@postgresql.org; Sat, 02 May 2015 14:25:08 +0000 Received: from mailin04.ims-firmen.de ([192.168.1.144]) by mailout01.ims-firmen.de with esmtp (envelope-from ) id 1YoYLn-0001vO-gf for pgsql-general@postgresql.org; Sat, 02 May 2015 16:25:03 +0200 Received: from [213.174.32.254] (helo=a-kretschmer.de) by mailin04.ims-firmen.de with esmtpsa (TLSv1:AES256-SHA:256) (envelope-from ) id 1YoYLk-000512-AG for pgsql-general@postgresql.org; Sat, 02 May 2015 16:25:03 +0200 Received: from kretschmer by a-kretschmer.de with local (Exim 4.69) (envelope-from ) id 1YoYLj-00017t-D0 for pgsql-general@postgresql.org; Sat, 02 May 2015 16:24:59 +0200 Date: Sat, 2 May 2015 16:24:59 +0200 From: Andreas Kretschmer To: pgsql-general@postgresql.org Subject: Re: How to exclude blobs (large objects) from being loaded by pg_restore? Message-ID: <20150502142459.GA4086@tux> References: <5a847d77e03244c8aa84f65b98cbc33e@exch1.invera.com> <20150502153901.db26611a4c21d19f046b688c@wanadoo.fr> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <20150502153901.db26611a4c21d19f046b688c@wanadoo.fr> X-OS: Debian/GNU Linux - weil ich es mir Wert bin! X-GPG-Fingerprint: EE16 3C01 7B9C 10F7 2C8B 3B86 4DB3 D9EE 7F45 84DA X-Message-Flag: "Windows" is not the answer. "Windows" is the question and the answer is "no"! X-Lugdd: Gerd Kube X-Info: My name is root. Just root. And I am licensed to kill -9 User-Agent: Mutt/1.5.18 (2008-05-17) X-Pg-Spam-Score: -2.6 (--) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-general Precedence: bulk Sender: pgsql-general-owner@postgresql.org Vincent Veyron wrote: > On Fri, 1 May 2015 14:12:08 +0000 > Alanoly Andrews wrote: > > > Hello, > > > > We have a database that has been unloaded using pg_dump. This database has a table with a field defined as "lo". When restoring this database to another system, we want to avoid loading this particular table as it is very large (about 8GB of blob data) and is not needed on the target system. I tried the following: > > 1. Create a list of all the tables in the pg_dump file using the -l option of pg_restore > > 2. Edit out the lines corresponding to the said table (with the "lo" column) > > 3. Run the pg_restore with the -L option to use the edited list of tables. > > > > use the -T option of pg_dump? i think, this isn't a solution. i HAVE a complete dump, but now i need a restore without the lo - data. And - you can't create a new dump with -T for several reasons now. Andreas -- Really, I'm not out to destroy Microsoft. That will just be a completely unintentional side effect. (Linus Torvalds) "If I was god, I would recompile penguin with --enable-fly." (unknown) Kaufbach, Saxony, Germany, Europe. N 51.05082°, E 13.56889° -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general