DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
	h=message-id:date:from:to:subject:mime-version:content-type;
	b=RETw3+cqRlIkB4f9fO2piwFG4P0b6gVKGnBLf2UWgVhC7rsgHm4UeacjWP7ZlqhHCl
	+7/vpvOUnES0WNFUlfMnRMFM5OHYxiQfkpCfJgzu/XUi6qB5qHU6XBsfVFAGjTwVFdIE
	WlxyfTI81w0bMyUkREEscAMNgkzOl/vBegUX8=
Message-ID: <1d219a6f0807181005m20b6625dqa865c0b8ef3ef00c@mail.gmail.com>
Date: Fri, 18 Jul 2008 13:05:03 -0400
From: "Chris Hoover" <revoohc@gmail.com>
To: "pgsql-admin@postgresql.org Admin" <pgsql-admin@postgresql.org>
Subject: Questions on pg_dump
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_Part_59163_820263.1216400703796"

------=_Part_59163_820263.1216400703796
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

We are doing some additional testing of our backup strategy with the goal of
moving from the text dump to the custom format and have some questions about
pg_dump -Fc.

Question 1.  Why would the custom format be larger?  pg_dump -Fc -Z 0 this
morning was 88GB while the normal pg_dump last night was 82GB.  We have not
had that much growth in the few intervening hours.  We were expecting the
-Fc to be at the most the same size of the text dump, and really expecting
the -Fc to be smaller.  Any explanations?  (We are doing timing with various
levels of compression and with the use of external compression to see what
gives us the best compression/time, so that is why the -Z 0 test.)

Question 2.  With the -Fc, how can we verify a successful backup?  With the
normal pg_dump, we are examining the end of the file looking for:
--
-- PostgreSQL database dump complete
--

Is there any sort of token like that with the -Fc that can be used to verify
a successful backup?

Thanks,

Chris

------=_Part_59163_820263.1216400703796
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

<div dir="ltr">We are doing some additional testing of our backup strategy with the goal of moving from the text dump to the custom format and have some questions about pg_dump -Fc.<br><br>Question 1.&nbsp; Why would the custom format be larger?&nbsp; pg_dump -Fc -Z 0 this morning was 88GB while the normal pg_dump last night was 82GB.&nbsp; We have not had that much growth in the few intervening hours.&nbsp; We were expecting the -Fc to be at the most the same size of the text dump, and really expecting the -Fc to be smaller.&nbsp; Any explanations?&nbsp; (We are doing timing with various levels of compression and with the use of external compression to see what gives us the best compression/time, so that is why the -Z 0 test.)<br>
<br>Question 2.&nbsp; With the -Fc, how can we verify a successful backup?&nbsp; With the normal pg_dump, we are examining the end of the file looking for:<br>--<br>-- PostgreSQL database dump complete<br>--<br><br>Is there any sort of token like that with the -Fc that can be used to verify a successful backup?<br>
<br>Thanks,<br><br>Chris<br><br></div>

------=_Part_59163_820263.1216400703796--