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

Re: 7 hrs for a pg_restore?

From: Douglas J Hunley <doug(at)hunley(dot)homeip(dot)net>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Richard Huxton <dev(at)archonet(dot)com>, pgsql-performance(at)postgresql(dot)org
Subject: Re: 7 hrs for a pg_restore?
Date: 2008-02-19 19:08:23
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-performance
On Tuesday 19 February 2008 13:22:58 Tom Lane wrote:
> Richard Huxton <dev(at)archonet(dot)com> writes:
> > Douglas J Hunley wrote:
> >> I spent a whopping seven hours restoring a database late Fri nite for a
> >
> > Oh, and have you tweaked the configuration settings for the restore?
> > Lots of work_mem, turn fsync off, that sort of thing.
> maintenance_work_mem, to be more specific.  If that's too small it will
> definitely cripple restore speed.  I'm not sure fsync would make much
> difference, but checkpoint_segments would.  See

from the postgresql.conf i posted:
~ $ grep maint postgresql.conf 
maintenance_work_mem = 256MB            # min 1MB

thx for the pointer to the URL. I've made note of the recommendations therein 
for next time.

> Also: why did you choose -o ... was there a real need to?  I can see
> that being pretty expensive.

I was under the impression our application made reference to OIDs. I'm now 
doubting that heavily <g> and am seeking confirmation.

Douglas J Hunley (doug at - Linux User #174778

I've got trouble with the wife again - she came into the bar looking for me 
and I asked her for her number.

In response to

pgsql-performance by date

Next:From: Douglas J HunleyDate: 2008-02-19 19:20:11
Subject: Re: 7 hrs for a pg_restore?
Previous:From: Douglas J HunleyDate: 2008-02-19 19:00:56
Subject: Re: 7 hrs for a pg_restore?

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