From: Dimitri Fontaine <dimitri@2ndQuadrant.fr>
To: "Jehan-Guillaume \(ioguix\) de Rorthais" <ioguix@free.fr>
Cc: mark <dvlhntr@gmail.com>, 'Martin Povolny' <martin.povolny@solnet.cz>,
	pgsql-admin@postgresql.org
Subject: Re: large database: problems with pg_dump and pg_restore
Organization: 2ndQuadrant
References: <E1PAhuU-0006Fa-DI@ns.solnet.cz>
	<68B59BEDCD36854AADBDF17E91B2937A01A7166E97@EXCHMAIL.staff.internode.com.au>
	<4CC75485.4080901@free.fr> <005a01cb7580$7a9749f0$6fc5ddd0$@com>
	<4CC7F43E.7010106@free.fr>
User-Mail-Address: dimitri@2ndQuadrant.fr
Date: Sun, 31 Oct 2010 19:45:53 +0100
In-Reply-To: <4CC7F43E.7010106@free.fr> (Jehan-Guillaume de Rorthais's message
	of "Wed, 27 Oct 2010 11:43:26 +0200")
Message-ID: <m2ocaaciam.fsf@2ndQuadrant.fr>
User-Agent: Gnus/5.110011 (No Gnus v0.11) Emacs/24.0.50 (darwin)
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable

"Jehan-Guillaume (ioguix) de Rorthais" <ioguix@free.fr> writes:
> If you can spend some more time using -Fc, then you'll be able to play
> with -l and -L switches of pg_restore to optionally decide what should
> be restored or not (with more control than -n, -t, etc, think about
> excluding slony stuffs as instance)

See also pg_staging that implements some commands for pg_restore
filtering by schema. You can use that feature on its own.

  http://github.com/dimitri/pg_staging
  http://tapoueh.org/articles/blog/_pg_staging's_bird_view.html
  http://tapoueh.org/pgstaging.html

Ok, for now check the docs, later I'll try to blog about some features
in pg_staging that you can use on their own, and maybe some more about
getting up to speed with pg_staging, after all.