Date: Wed, 14 Jul 2010 14:35:33 -0700
From: David Kerr <dmk@mr-paradox.net>
To: "Burgholzer, Robert (DEQ)" <Robert.Burgholzer@deq.virginia.gov>
Cc: pgsql-admin@postgresql.org
Subject: Re: proper tuning for restoring from pg_dump in 8.3.7
Message-ID: <20100714213533.GA43630@mr-paradox.net>
References: <4C3DCFCE02000025000335CD@gw.wicourts.gov>
	<4C3DD27702000025000335D0@gw.wicourts.gov>
	<4C3DD27702000025000335D0@gw.wicourts.gov>
	<B6C40D17104BEF47B1CB85623CDFAC63896286@COVMSGCES-EMB13.cov.virginia.gov>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: 
 <B6C40D17104BEF47B1CB85623CDFAC63896286@COVMSGCES-EMB13.cov.virginia.gov>
User-Agent: Mutt/1.4.2.3i

On Wed, Jul 14, 2010 at 05:30:17PM -0400, Burgholzer, Robert (DEQ) wrote:
- >.  The options I suggested be turned off just for the load process 
- > ...
- > not safe if the other databases are in the same PostgreSQL Cluster
- 
- They are, so I won't --- thanks for the heads up on that too.
- 
- Just for posterity, here is the systems specs (from my hardware guy):
- DEQ1 is on centos 5.3
- W/ 1.5Tb striped system volumes using a pair of standard 7600 rpm sata
- drives.  These are on system 3 gbit/s ports.

So that makes total sense. you're flooding your disks/controller doing 
the massive amount of writing that's involved with the restore.

Dave