Skip site navigation (1) Skip section navigation (2)

Re: 7 hrs for a pg_restore?

From: Jeff Davis <pgsql(at)j-davis(dot)com>
To: Douglas J Hunley <doug(at)hunley(dot)homeip(dot)net>
Cc: pgsql-performance(at)postgresql(dot)org
Subject: Re: 7 hrs for a pg_restore?
Date: 2008-02-19 18:23:23
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-performance
On Tue, 2008-02-19 at 13:03 -0500, 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. 

Are there lots of indexes on localized text attributes? If you have a
big table with localized text (e.g. en_US.UTF-8), it can take a long
time to build the indexes. If the file is 5GB compressed, I wouldn't be
surprised if it took a long time to restore.

Keep in mind, if you have several GB worth of indexes, they take up
basically no space in the logical dump (just the "CREATE INDEX" command,
and that's it). But they can take a lot of processor time to build up
again, especially with localized text.

	Jeff Davis

In response to


pgsql-performance by date

Next:From: Douglas J HunleyDate: 2008-02-19 18:58:38
Subject: Re: 7 hrs for a pg_restore?
Previous:From: Tom LaneDate: 2008-02-19 18:22:58
Subject: Re: 7 hrs for a pg_restore?

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group