pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Joseph McClintock <joe.mcclintock@antics.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: pgsql-admin@postgresql.org
Subject: Re: Very Very Slow Database Restore
Date: Thu, 21 Dec 2006 09:43:23 -0800
Message-ID: <1166723003.4208.6.camel@mcclintock.anticsoffline.com> (raw)
In-Reply-To: <14149.1166680064@sss.pgh.pa.us>
References: <1166646860.3941.4.camel@mcclintock.anticsoffline.com>
	<14149.1166680064@sss.pgh.pa.us>

Thanks for the feed back.  Doubling the work_men from 10240 to 20480
seemed to make the process faster but then I ran out of disk space.
Shared buffers are at 2000 which I can try increasing.

I now need to move the database off the system partition to my working
partition which has more space.  I hope don't have to re-install
Postges, that would be a real bummer.

--Joe   

On Thu, 2006-12-21 at 00:47 -0500, Tom Lane wrote:
> Joseph McClintock <joe.mcclintock@antics.com> writes:
> > Now our database has grown and the pg_dump give me a 2.1 GB file which
> > is taking 12 hours or more to restore, Yickes! I've tried compressing
> > the dump file:
> 
> Compressing the dump file will make the restore slower, most likely,
> because of the extra CPU effort to decompress.  It certainly won't
> create any great savings.
> 
> > The database configuration is pretty much out of the box.
> 
> You probably want to increase maintenance_work_mem (to speed index
> creation) and checkpoint_segments (general rule for any update-intensive
> situation) ... and for 8.0 you'd maybe need larger shared_buffers etc.
> The postgresql techdocs website has lots of general advice about
> parameter settings --- the only thing specific to restore is you
> want high maintenance_work_mem.
> 
> 			regards, tom lane





view thread (4+ messages)  latest in thread

Message-ID: <1166723003.4208.6.camel@mcclintock.anticsoffline.com>
Permalink:  ../1166723003.4208.6.camel@mcclintock.anticsoffline.com/
Also on:    postgresql.org/message-id/1166723003.4208.6.camel@mcclintock.anticsoffline.com

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-admin@postgresql.org
  Cc: joe.mcclintock@antics.com, tgl@sss.pgh.pa.us
  Subject: Re: Very Very Slow Database Restore
  In-Reply-To: <1166723003.4208.6.camel@mcclintock.anticsoffline.com>
  References: <1166646860.3941.4.camel@mcclintock.anticsoffline.com> <14149.1166680064@sss.pgh.pa.us> <1166723003.4208.6.camel@mcclintock.anticsoffline.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox