X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org
Received: from localhost (av.hub.org [200.46.204.144])
	by postgresql.org (Postfix) with ESMTP id 635B511F66F2
	for <pgsql-performance-postgresql.org@localhost.postgresql.org>;
	Mon, 10 Apr 2006 12:43:24 -0300 (ADT)
X-Virus-Scanned: by amavisd-new at hub.org
X-Spam-Score: 0.12
X-Spam-Level: 
X-Spam-Status: No, score=0.12 required=5 tests=[AWL=0.119, HTML_MESSAGE=0.001]
Received: from postgresql.org ([200.46.204.71])
	by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024)
	with ESMTP id ZrSCey0s4Zyb
	for <pgsql-performance-postgresql.org@localhost.postgresql.org>;
	Mon, 10 Apr 2006 12:42:29 -0300 (ADT)
X-Greylist: domain auto-whitelisted by SQLgrey-
Received: from nproxy.gmail.com (nproxy.gmail.com [64.233.182.184])
	by postgresql.org (Postfix) with ESMTP id AA57F11F68ED
	for <pgsql-performance@postgresql.org>;
	Mon, 10 Apr 2006 12:42:07 -0300 (ADT)
Received: by nproxy.gmail.com with SMTP id p77so628666nfc
	for <pgsql-performance@postgresql.org>;
	Mon, 10 Apr 2006 08:42:05 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com;
	h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:references;
	b=Pez2by/R9KgJ+0AI0PWzxC/byW7cDlJvsoz0lgrBpwN5kVpsWjBVYf0ZgVUdLIDHwsEmIGCsCJ9Av2VPMCFPLk5TV5FiXlibE2T3H/+SEIu6E0dZnVKYK/fFG9ZpGRPIQ02ZbCQ1+Y55w5OrtqgED6MhDgXt5t350hXybkVkWFM=
Received: by 10.49.15.4 with SMTP id s4mr1818938nfi;
	Mon, 10 Apr 2006 08:42:03 -0700 (PDT)
Received: by 10.49.27.16 with HTTP; Mon, 10 Apr 2006 08:42:02 -0700 (PDT)
Message-ID: <a97c77030604100842m6f2adb4hbab87344c48901e@mail.gmail.com>
Date: Mon, 10 Apr 2006 21:12:02 +0530
From: "Rajesh Kumar Mallah" <mallah.rajesh@gmail.com>
To: "Jesper Krogh" <jesper@krogh.cc>
Subject: Re: Restore performance?
Cc: pgsql-performance@postgresql.org
In-Reply-To: <a97c77030604100839p2c4b15c9q88f1258287a0e6d0@mail.gmail.com>
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_Part_24390_12094072.1144683722990"
References: <e1d31l$2nt$1@sea.gmane.org>
	<a97c77030604100839p2c4b15c9q88f1258287a0e6d0@mail.gmail.com>
X-Archive-Number: 200604/206
X-Sequence-Number: 18290

------=_Part_24390_12094072.1144683722990
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

sorry for the post , i didn' saw the other replies only after posting.

On 4/10/06, Rajesh Kumar Mallah <mallah.rajesh@gmail.com> wrote:
>
>
>
> On 4/10/06, Jesper Krogh <jesper@krogh.cc> wrote:
> >
> > Hi
> >
> > I'm currently upgrading a Posgresql 7.3.2 database to a
> > 8.1.<something-good>
> >
> > I'd run pg_dump | gzip > sqldump.gz  on the old system. That took about
> > 30 hours and gave me an 90GB zipped file. Running
> > cat sqldump.gz | gunzip | psql
> > into the 8.1 database seems to take about the same time. Are there
> > any tricks I can use to speed this dump+restore process up?
>
>
> was the last restore successfull ?
> if so why do you want to repeat ?
>
> some tips
>
> 1. run new version of postgres in a different port and pipe pg_dump to
> psql
> this may save the CPU time of compression , there is no need for a
> temporary
> dump file.
>
> pg_dump | /path/to/psql813  -p 54XX newdb
>
> 2. use new version of pg_dump to dump the old database as new version
>     is supposed to be wiser.
>
> 3. make sure you are trapping the restore errors properly
> psql newdb 2>&1 | cat | tee err works for me.
>
>
>
>
> The database contains quite alot of BLOB, thus the size.
> >
> > Jesper
> > --
> > ./Jesper Krogh, jesper@krogh.cc, Jabber ID: jesper@jabbernet.dk
> >
> >
> >
> > ---------------------------(end of broadcast)--------------------------=
-
> >
> > TIP 6: explain analyze is your friend
> >
>
>

------=_Part_24390_12094072.1144683722990
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

sorry for the post , i didn' saw the other replies only after posting.<br><=
br><div><span class=3D"gmail_quote">On 4/10/06, <b class=3D"gmail_sendernam=
e">Rajesh Kumar Mallah</b> &lt;<a href=3D"mailto:mallah.rajesh@gmail.com">m=
allah.rajesh@gmail.com
</a>&gt; wrote:</span><blockquote class=3D"gmail_quote" style=3D"border-lef=
t: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1=
ex;"><div style=3D"direction: ltr;"><br><br><div></div><div style=3D"direct=
ion: ltr;">
<span class=3D"q"><span class=3D"gmail_quote">On 4/10/06, <b class=3D"gmail=
_sendername">Jesper Krogh</b> &lt;<a href=3D"mailto:jesper@krogh.cc" target=
=3D"_blank" onclick=3D"return top.js.OpenExtLink(window,event,this)">jesper=
@krogh.cc
</a>&gt; wrote:</span><blockquote class=3D"gmail_quote" style=3D"border-lef=
t: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1=
ex;">
Hi<br><br>I'm currently upgrading a Posgresql 7.3.2 database to a<br>8.1.&l=
t;something-good&gt;<br><br>I'd run pg_dump | gzip &gt; sqldump.gz&nbsp;&nb=
sp;on the old system. That took about<br>30 hours and gave me an 90GB zippe=
d file. Running
<br>cat sqldump.gz | gunzip | psql<br>into the 8.1 database seems to take a=
bout the same time. Are there<br>any tricks I can use to speed this dump+re=
store process up?</blockquote></span></div><div style=3D"direction: ltr;">
<div><br>was the last restore successfull ?=20
<br>if so why do you want to repeat ?<br><br>some tips<br><br>1. run new ve=
rsion of postgres in a different port and pipe pg_dump to psql<br>this may =
save the CPU time of compression , there is no need for a temporary<br>

dump file.<br><br>pg_dump | /path/to/psql813&nbsp; -p 54XX newdb<br><br>2. =
use new version of pg_dump to dump the old database as new version<br>&nbsp=
; &nbsp; is supposed to be wiser.<br><br>3. make sure you are trapping the =
restore errors properly
<br>psql newdb 2&gt;&amp;1 | cat | tee err works for me.<br><br><br>&nbsp;<=
/div></div><div style=3D"direction: ltr;"><span class=3D"q"><br><blockquote=
 class=3D"gmail_quote" style=3D"border-left: 1px solid rgb(204, 204, 204); =
margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
The database contains quite alot of BLOB, thus the size.
<br><br>Jesper<br>--<br>./Jesper Krogh, <a href=3D"mailto:jesper@krogh.cc" =
target=3D"_blank" onclick=3D"return top.js.OpenExtLink(window,event,this)">=
jesper@krogh.cc</a>, Jabber ID: <a href=3D"mailto:jesper@jabbernet.dk" targ=
et=3D"_blank" onclick=3D"return top.js.OpenExtLink(window,event,this)">
jesper@jabbernet.dk</a><br><br><br><br>---------------------------(end of b=
roadcast)---------------------------
<br>TIP 6: explain analyze is your friend<br></blockquote></span></div><div=
 style=3D"direction: ltr;"></div><br>

</div></blockquote></div><br>

------=_Part_24390_12094072.1144683722990--