DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com;
	h=X-YMail-OSG:Received:X-Mailer:References:Message-ID:Date:From:Reply-To:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding;
	b=FPGxF5p/uvsJJ6fv3qrNv5rZ/iKhd7HaqMgUrVYT9nT4taEcSOo4ziRdbZtx6NK1mFvOknyRtddo9Ia3uJSInRC+QEWFhGuVSeTU5BS//ML8p41HCdag9ghto/mjGCxqBtibEcfdG2yJm81InNXwnhV5T5TarctcEGK8VnCKnuA=;
References: <877182.59904.qm@web39704.mail.mud.yahoo.com>
	<2813.1309547390@sss.pgh.pa.us>
Message-ID: <1309548592.2550.YahooMailNeo@web39706.mail.mud.yahoo.com>
Date: Fri, 1 Jul 2011 12:29:52 -0700 (PDT)
From: Bob Lunney <bob_lunney@yahoo.com>
Reply-To: Bob Lunney <bob_lunney@yahoo.com>
Subject: Re: Parallel pg_dump on a single database 
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: "pgsql-admin@postgresql.org" <pgsql-admin@postgresql.org>
In-Reply-To: <2813.1309547390@sss.pgh.pa.us>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable

Tom,=0A=0AThanks for the response, but I figured out the error is mine, not=
 pg_dump's. =A0In short (to minimize my embarrassment!) don't write to the =
same file from three different pg_dumps.=A0=0A=0AThe good news is running m=
ultiple pg_dumps simultaneously on a single database with exclusive coverag=
e of different table sets works great, and my overall dump times have been =
reduced to one-fifth the time it takes to run a single pg_dump. =A0=0A=0ABT=
W, I'm using PG 8.4.1, going to 8.4.8 soon, and its working great. =A0Thank=
s to all for the excellent database software.=0A=0A=0ARegards,=0A=0ABob Lun=
ney=0A=0A________________________________=0AFrom: Tom Lane <tgl@sss.pgh.pa.=
us>=0ATo: Bob Lunney <bob_lunney@yahoo.com>=0ACc: "pgsql-admin@postgresql.o=
rg" <pgsql-admin@postgresql.org>=0ASent: Friday, July 1, 2011 2:09 PM=0ASub=
ject: Re: [ADMIN] Parallel pg_dump on a single database =0A=0ABob Lunney <b=
ob_lunney@yahoo.com> writes:=0A> Is it possible (or smart!) to run multiple=
 pg_dumps simulataneously on a single database, dumping different parts of =
the database to different files by using table and schema exclusion?=A0 I'm=
 attempting this and sometimes it works and sometimes when I check the dump=
 files with =0A>=A0=A0=A0pg_restore -Fc <dumpfile> > /dev/null=0A=0A> I get=
 =0A=0A>=A0=A0=A0pg_restore: [custom archiver] found unexpected block ID (4=
) when reading data -- expected 4238=0A=0AThat sure sounds like a bug.=A0 W=
hat PG version are you using exactly?=0ACan you provide a more specific des=
cription of what you're doing,=0Aso somebody else could reproduce this?=0A=
=0A=A0=A0=A0 =A0=A0=A0 =A0=A0=A0 regards, tom lane