Message-ID: <47BB1C51.6010203@archonet.com>
Date: Tue, 19 Feb 2008 18:13:37 +0000
From: Richard Huxton <dev@archonet.com>
User-Agent: Thunderbird 2.0.0.9 (X11/20071031)
MIME-Version: 1.0
To: Douglas J Hunley <doug@hunley.homeip.net>
CC: pgsql-performance@postgresql.org
Subject: Re: 7 hrs for a pg_restore?
References: <200802191303.58840.doug@hunley.homeip.net>
In-Reply-To: <200802191303.58840.doug@hunley.homeip.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Douglas J Hunley wrote:
> I spent a whopping seven hours restoring a database late Fri nite for a 
> client. We stopped the application, ran pg_dump -v -Ft -b -o $db > 
> ~/pre_8.3.tar on the 8.2.x db, and then upgrading the software to 8.3. I then 
> did a pg_restore -v -d $db ./pre_8.3.tar and watched it positively crawl.
> I'll grant you that it's a 5.1G tar file, but 7 hours seems excessive. 

Depends, both on the machine and the database.

What sort of disk i/o are you seeing, what's the cpu(s) doing, and 
what's the restore taking so long over (since you have -v)?

Oh, and have you tweaked the configuration settings for the restore? 
Lots of work_mem, turn fsync off, that sort of thing.

-- 
   Richard Huxton
   Archonet Ltd