pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Tom Lane <tgl@sss.pgh.pa.us>
To: patrick keshishian <pkeshish@gmail.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: pg 7.4.x - pg_restore impossibly slow
Date: Thu, 13 Apr 2006 00:46:51 -0400
Message-ID: <9585.1144903611@sss.pgh.pa.us> (raw)
In-Reply-To: <53b425b00604121826x213fe2fdmc793e22026469923@mail.gmail.com>
References: <53b425b00604121826x213fe2fdmc793e22026469923@mail.gmail.com>

"patrick keshishian" <pkeshish@gmail.com> writes:
> My dev box is much slower hardware than the customer's
> server.  Even with that difference I expected to be able to
> pg_restore the database within one day.  But no.

Seems a bit odd.  Can you narrow down more closely which step of the
restore is taking the time?  (Try enabling log_statements.)

One thought is that kicking up work_mem and vacuum_mem is likely to
help for some steps (esp. CREATE INDEX and foreign-key checking).
And be sure you've done the usual tuning for write-intensive activity,
such as bumping up checkpoint_segments.  Turning off fsync wouldn't
be a bad idea either.

			regards, tom lane



view thread (7+ messages)  latest in thread

Message-ID: <9585.1144903611@sss.pgh.pa.us>
Permalink:  ../9585.1144903611@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/9585.1144903611@sss.pgh.pa.us

 · 

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 using the --to and --cc options:
  reply via email

  To: pgsql-performance@postgresql.org
  Cc: tgl@sss.pgh.pa.us, pkeshish@gmail.com
  Subject: Re: pg 7.4.x - pg_restore impossibly slow
  In-Reply-To: <9585.1144903611@sss.pgh.pa.us>

* 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