From: Tom Lane <tgl@sss.pgh.pa.us>
To: Bruno Wolff III <bruno@wolff.to>
Cc: D Kavan <bitsandbytes88@hotmail.com>
Cc: pgsql-admin@postgresql.org
Subject: Re: pg_restore
Date: Thu, 11 Aug 2005 17:56:15 -0400
Message-ID: <24171.1123797375@sss.pgh.pa.us> (raw)
In-Reply-To: <20050811204603.GA2886@wolff.to>
References: <BAY102-F2E0B7279722C1B5AF3904D1BD0@phx.gbl>
<20050811204603.GA2886@wolff.to>
Bruno Wolff III <bruno@wolff.to> writes:
>> psql dbname < dump_file
>> pg_restore -d test_restore_2 -Fc niehs_dump.backup
> Some things you can do are to turn off fsync for the restore and not
> restore foreign key contsraints and indexes until after the database
> has been loaded.
pg_dump/pg_restore should get the ordering considerations right already.
fsync off might help some but I'm not convinced of it. I'd look at the
value of maintenance_work_mem --- increasing that to maybe a few hundred
Mb would help the speed of index builds and foreign key checks.
But really what you ought to do first is find out where it's spending
its time. Can you run the restore with query logging and duration
logging enabled?
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-admin@postgresql.org
Cc: tgl@sss.pgh.pa.us, bruno@wolff.to, bitsandbytes88@hotmail.com
Subject: Re: pg_restore
In-Reply-To: <24171.1123797375@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