X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (av.hub.org [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id DC53FD7DD4 for ; Wed, 12 Oct 2005 10:36:07 -0300 (ADT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 06057-08 for ; Wed, 12 Oct 2005 13:36:00 +0000 (GMT) Received: from xproxy.gmail.com (xproxy.gmail.com [66.249.82.206]) by svr1.postgresql.org (Postfix) with ESMTP id 7D0BCD7DAD for ; Wed, 12 Oct 2005 10:36:02 -0300 (ADT) Received: by xproxy.gmail.com with SMTP id s6so67079wxc for ; Wed, 12 Oct 2005 06:36:07 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:mime-version:content-type; b=o8NFIPV8//MmI+WboHyVZVRKHpROYE6p1YFvP9+fsIuFf9nL+SRzYY1Fa2/AzItprwpQE33fynFpPfkj40jAk04BEd5odaduR6kZp/DS8Q34bGGrKlzIIDFYJuqRFTgH21FA+nOfkfQ7x+L/rpgvC+F+CZis7/4WexblZH+9Vtc= Received: by 10.70.9.12 with SMTP id 12mr158277wxi; Wed, 12 Oct 2005 06:36:07 -0700 (PDT) Received: by 10.70.87.15 with HTTP; Wed, 12 Oct 2005 06:36:07 -0700 (PDT) Message-ID: <1d219a6f0510120636h353fa8f5s134407c004e15096@mail.gmail.com> Date: Wed, 12 Oct 2005 09:36:07 -0400 From: Chris Hoover To: pgsql-admin@postgresql.org Subject: help with pg_dump timings MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_8957_13584846.1129124167167" X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.378 required=5 tests=[AWL=0.058, HTML_10_20=0.295, HTML_MESSAGE=0.001, RCVD_BY_IP=0.024] X-Spam-Level: X-Archive-Number: 200510/134 X-Sequence-Number: 19206 ------=_Part_8957_13584846.1129124167167 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline I'm wondering, does anyone know of any timing tests for pg_dump? I am trying to find the fastest way to do our nightly database backups usin= g pg_dump. And I just wanted to make sure I don't reinvent the wheel if someone has already done a bunch of comparisions with the various ways to backup. Here are the kind of timings I'm looking at: pg_dump -Fc -Zx pg_dump -Fc pg_dump -Ft pg_dump pg_dump -Fc | gzip > backup pg_dump -Ft | gzip > backup pg_dump | gzip > backup pg_dump -Fc | bzip2 > backup pg_dump -Ft | bzip2 > backup pg_dump | bzip2 > backup I know there are many variables, but I'm just looking at the pg_dump process. Does anyone know what the fastest pg_dump would be? Also, what -Z compression level equals the compression of gzip? I've played with -Z9, but it seems to compress better than gzip (but takes a bit longer). Thanks, Chris ------=_Part_8957_13584846.1129124167167 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline I'm wondering, does anyone know of any timing tests for pg_dump?

I am trying to find the fastest way to do our nightly database backups using pg_dump.  And I just wanted to make sure I don't reinvent the wheel if someone has already done a bunch of comparisions with the various ways to backup.

Here are the kind of timings I'm looking at:

pg_dump -Fc -Zx
pg_dump -Fc
pg_dump -Ft
pg_dump
pg_dump -Fc | gzip > backup
pg_dump -Ft | gzip > backup
pg_dump | gzip > backup
pg_dump -Fc | bzip2 > backup
pg_dump -Ft | bzip2 > backup
pg_dump | bzip2 > backup

I know there are many variables, but I'm just looking at the pg_dump process.  Does anyone know what the fastest pg_dump would be?

Also, what -Z compression level equals the compression of gzip?  I've played with -Z9, but it seems to compress better than gzip (but takes a bit longer).

Thanks,

Chris
------=_Part_8957_13584846.1129124167167--