DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com;
	h=Message-ID:X-YMail-OSG:Received:X-Mailer:Date:From:Subject:To:In-Reply-To:MIME-Version:Content-Type;
	b=nw3EuaycdVyO69i8flMhK2371vtGTpRBpmJxhI+BdhHneyDkTKH3OS1GFgnHTuPBo8kMR/OUrk+jmdgV3kyQ4B1l8UbWuG/0yQnsZbgioesQ7IRlBfbp2Ush+4Mu1pHg5odrOSL0wLCP8wocoOSFNUYLk2F/dgPq7FY4x0AEeAE=;
Message-ID: <336456.89598.qm@web39705.mail.mud.yahoo.com>
Date: Tue, 26 Oct 2010 08:33:14 -0700 (PDT)
From: Bob Lunney <bob_lunney@yahoo.com>
Subject: Re: pg_dump/restore problems
To: pgsql-admin@postgresql.org, Glen Brown <gkbrown22@gmail.com>
In-Reply-To: <fb9f1c031002151025u52dd27c7w344d5c9e7a65748f@mail.gmail.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="0-1882136753-1288107194=:89598"

--0-1882136753-1288107194=:89598
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable

Glen,
Did you drop the indexes prior to the restore? =A0If not, try doing so and =
recreating the indexes afterwards. =A0That will also speed up the data load=
.
Bob Lunney

--- On Mon, 2/15/10, Glen Brown <gkbrown22@gmail.com> wrote:

From: Glen Brown <gkbrown22@gmail.com>
Subject: [ADMIN] pg_dump/restore problems
To: pgsql-admin@postgresql.org
Date: Monday, February 15, 2010, 1:25 PM

I am not sure where I should post this but I am running into problems tryin=
g to restore a large table. I am running 8.4.1 on all servers. The table is=
 about 25gb in size and most of that is toasted. It has about 2.5m records.=
 When I dump this table using pg_dump -Fc it creates a 15 gb file. I am try=
ing to restore in into a database that has 100gb of free disk space and it =
consumes it all and fails to finish the restore. The table is not partition=
ed and has a few indexes on it. What can I do?=0A=0A=A0=0Athanks=0A-glen=0A
Glen Brown
=0A=0A=0A=0A      
--0-1882136753-1288107194=:89598
Content-Type: text/html; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable

<table cellspacing=3D"0" cellpadding=3D"0" border=3D"0" ><tr><td valign=3D"=
top" style=3D"font: inherit;">Glen,<div><br></div><div>Did you drop the ind=
exes prior to the restore? &nbsp;If not, try doing so and recreating the in=
dexes afterwards. &nbsp;That will also speed up the data load.</div><div><b=
r></div><div>Bob Lunney<br><br>--- On <b>Mon, 2/15/10, Glen Brown <i>&lt;gk=
brown22@gmail.com&gt;</i></b> wrote:<br><blockquote style=3D"border-left: 2=
px solid rgb(16, 16, 255); margin-left: 5px; padding-left: 5px;"><br>From: =
Glen Brown &lt;gkbrown22@gmail.com&gt;<br>Subject: [ADMIN] pg_dump/restore =
problems<br>To: pgsql-admin@postgresql.org<br>Date: Monday, February 15, 20=
10, 1:25 PM<br><br><div id=3D"yiv795675939"><div>I am not sure where I shou=
ld post this but I am running into problems trying to restore a large table=
. I am running 8.4.1 on all servers. The table is about 25gb in size and mo=
st of that is toasted. It has about 2.5m records. When I dump this table us=
ing
 pg_dump -Fc it creates a 15 gb file. I am trying to restore in into a data=
base that has 100gb of free disk space and it consumes it all and fails to =
finish the restore. The table is not partitioned and has a few indexes on i=
t. What can I do?</div>=0A=0A<div>&nbsp;</div>=0A<div>thanks</div>=0A<div>-=
glen</div>=0A<div><br clear=3D"all">Glen Brown<br></div>=0A</div></blockquo=
te></div></td></tr></table><br>=0A=0A=0A=0A=0A=0A=0A=0A      
--0-1882136753-1288107194=:89598--