From: Tom Lane <tgl@sss.pgh.pa.us>
To: Richard Huxton <dev@archonet.com>
Cc: Douglas J Hunley <doug@hunley.homeip.net>
Cc: pgsql-performance@postgresql.org
Subject: Re: 7 hrs for a pg_restore?
Date: Tue, 19 Feb 2008 13:22:58 -0500
Message-ID: <19241.1203445378@sss.pgh.pa.us> (raw)
In-Reply-To: <47BB1C51.6010203@archonet.com>
References: <200802191303.58840.doug@hunley.homeip.net>
<47BB1C51.6010203@archonet.com>
Richard Huxton <dev@archonet.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
http://www.postgresql.org/docs/8.3/static/populate.html#POPULATE-PG-DUMP
Also: why did you choose -o ... was there a real need to? I can see
that being pretty expensive.
regards, tom lane
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, dev@archonet.com, doug@hunley.homeip.net
Subject: Re: 7 hrs for a pg_restore?
In-Reply-To: <19241.1203445378@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