X-Original-To: pgsql-performance-postgresql.org@postgresql.org
Received: from localhost (mx1.hub.org [200.46.208.251])
	by postgresql.org (Postfix) with ESMTP id C9DDC9FA5C8
	for <pgsql-performance-postgresql.org@postgresql.org>;
	Wed, 14 Jun 2006 18:16:26 -0300 (ADT)
Received: from postgresql.org ([200.46.204.71])
	by localhost (mx1.hub.org [200.46.208.251]) (amavisd-new, port 10024)
	with ESMTP id 73520-03 for
	<pgsql-performance-postgresql.org@postgresql.org>;
	Wed, 14 Jun 2006 18:16:22 -0300 (ADT)
X-Greylist: domain auto-whitelisted by SQLgrey-
Received: from ug-out-1314.google.com (ug-out-1314.google.com [66.249.92.170])
	by postgresql.org (Postfix) with ESMTP id C44109FA3D7
	for <pgsql-performance@postgresql.org>;
	Wed, 14 Jun 2006 18:16:22 -0300 (ADT)
Received: by ug-out-1314.google.com with SMTP id a2so543522ugf
	for <pgsql-performance@postgresql.org>;
	Wed, 14 Jun 2006 14:16:20 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com;
	h=received:message-id:date:from:reply-to:sender:to:subject:cc:in-reply-to:mime-version:content-type:references:x-google-sender-auth;
	b=Lq+UYRfb2HN57Jj/tAchq4Mz1wwPLCo854I0pj8KS1A/OGtoVsUoF5VrwWesyc9Uy2F4wBrlZMqrMZcA+K6wAS74EsLrqOpHwA6ziXahPUk55SPbDsLvOH8zi80kG8rpzXsoEtk36E+pGmR2OHyIT8vqsgcwksWacTHkaXKxmrU=
Received: by 10.66.216.6 with SMTP id o6mr1062230ugg;
	Wed, 14 Jun 2006 14:16:20 -0700 (PDT)
Received: by 10.66.216.11 with HTTP; Wed, 14 Jun 2006 14:16:19 -0700 (PDT)
Message-ID: <c841561b0606141416w3c5cee35mc05d219700027755@mail.gmail.com>
Date: Wed, 14 Jun 2006 17:16:19 -0400
From: "John Vincent" <pgsql-performance@lusis.org>
Reply-To: pgsql-performance@lusis.org
To: "Scott Marlowe" <smarlowe@g2switchworks.com>
Subject: Re: Performance of pg_dump on PGSQL 8.0
Cc: "PGSQL Performance" <pgsql-performance@postgresql.org>
In-Reply-To: <1150319015.26538.45.camel@state.g2switchworks.com>
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_Part_12490_12012128.1150319779973"
References: <44902165.7020502@lusis.org>
	<1150303450.26538.9.camel@state.g2switchworks.com>
	<c841561b0606141111g9244024oc091c58ecf0e1d94@mail.gmail.com>
	<c841561b0606141256j11605d51m67abfd8467ceae1e@mail.gmail.com>
	<c841561b0606141359g5a0cefa7j8641486f1787445b@mail.gmail.com>
	<1150319015.26538.45.camel@state.g2switchworks.com>
X-Google-Sender-Auth: 899db6d545f6b27b
X-Virus-Scanned: Maia Mailguard 1.0.1
X-Archive-Number: 200606/274
X-Sequence-Number: 19631

------=_Part_12490_12012128.1150319779973
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

time gzip -6 claDW_PGSQL.test.bak

real    3m4.360s
user    1m22.090s
sys     0m6.050s

Which is still less time than it would take to do a compressed pg_dump.

On 6/14/06, Scott Marlowe <smarlowe@g2switchworks.com> wrote:
>
> How long does gzip take to compress this backup?
>
> On Wed, 2006-06-14 at 15:59, John Vincent wrote:
> > Okay I did another test dumping using the uncompressed backup on the
> > system unloaded and the time dropped down to 8m for the backup.
> > There's still the size issue to contend with but as I said, I've got a
> > fair bit of space left on the SAN to work with.
>

------=_Part_12490_12012128.1150319779973
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

time gzip -6 claDW_PGSQL.test.bak<br><br>real&nbsp;&nbsp;&nbsp; 3m4.360s<br>user&nbsp;&nbsp;&nbsp; 1m22.090s<br>sys&nbsp;&nbsp;&nbsp;&nbsp; 0m6.050s<br><br>Which is still less time than it would take to do a compressed pg_dump. <br><br><div><span class="gmail_quote">On 6/14/06, 
<b class="gmail_sendername">Scott Marlowe</b> &lt;<a href="mailto:smarlowe@g2switchworks.com">smarlowe@g2switchworks.com</a>&gt; wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
How long does gzip take to compress this backup?<br><br>On Wed, 2006-06-14 at 15:59, John Vincent wrote:<br>&gt; Okay I did another test dumping using the uncompressed backup on the<br>&gt; system unloaded and the time dropped down to 8m for the backup.
<br>&gt; There's still the size issue to contend with but as I said, I've got a<br>&gt; fair bit of space left on the SAN to work with.<br></blockquote></div><br>

------=_Part_12490_12012128.1150319779973--