pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Douglas J Hunley <doug@hunley.homeip.net>
To: Jeff <threshar@threshar.is-a-geek.com>
Cc: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Richard Huxton <dev@archonet.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: 7 hrs for a pg_restore?
Date: Tue, 19 Feb 2008 15:55:43 -0500
Message-ID: <200802191555.43340.doug@hunley.homeip.net> (raw)
In-Reply-To: <F80D4D50-9F3F-4CAA-B01E-B644912126D7@torgo.978.org>
References: <200802191303.58840.doug@hunley.homeip.net>
	<19241.1203445378@sss.pgh.pa.us>
	<F80D4D50-9F3F-4CAA-B01E-B644912126D7@torgo.978.org>

On Tuesday 19 February 2008 15:07:30 Jeff wrote:
> On Feb 19, 2008, at 1:22 PM, Tom Lane wrote:
> > 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
> > http://www.postgresql.org/docs/8.3/static/populate.html#POPULATE-PG-
> > DUMP
>
> I wonder if it would be worthwhile if pg_restore could emit a warning
> if maint_work_mem is "low" (start flamewar on what "low" is).
>
> And as an addition to that - allow a cmd line arg to have pg_restore
> bump it before doing its work?  On several occasions I was moving a
> largish table and the COPY part went plenty fast, but when it hit
> index creation it slowed down to a crawl due to low maint_work_mem..

fwiw, I +1 this

now that I have a (minor) understanding of what's going on, I'd love to do 
something like:
pg_restore -WM $large_value <normal options>


-- 
Douglas J Hunley (doug at hunley.homeip.net) - Linux User #174778
http://doug.hunley.homeip.net

There are no dead students here. This week.



view thread (42+ messages)  latest in thread

Message-ID: <200802191555.43340.doug@hunley.homeip.net>
Permalink:  ../200802191555.43340.doug@hunley.homeip.net/
Also on:    postgresql.org/message-id/200802191555.43340.doug@hunley.homeip.net

 · 

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-performance@postgresql.org
  Cc: doug@hunley.homeip.net, threshar@threshar.is-a-geek.com, tgl@sss.pgh.pa.us, dev@archonet.com
  Subject: Re: 7 hrs for a pg_restore?
  In-Reply-To: <200802191555.43340.doug@hunley.homeip.net>
  References: <200802191303.58840.doug@hunley.homeip.net> <19241.1203445378@sss.pgh.pa.us> <F80D4D50-9F3F-4CAA-B01E-B644912126D7@torgo.978.org> <200802191555.43340.doug@hunley.homeip.net>

* 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