From: Eric Lam <elam@lisasoft.com>
To: pgsql-performance@postgresql.org
Subject: Slow restoration question
Date: Wed, 26 Apr 2006 17:14:41 +0930
Message-ID: <444F24E9.2010907@lisasoft.com> (raw)
Hello list,
what is the quickest way of dumping a DB and restoring it? I have done a
"pg_dump -D database | split --line-bytes 1546m part"
Restoration as
"cat part* | psql database 2> errors 1>/dev/null"
all dumpfiles total about 17Gb. It has been running for 50ish hrs and up
to about the fourth file (5-6 ish Gb) and this is on a raid 5 server.
A while back I did something similar for a table with where I put all
the insert statements in one begin/end/commit block, this slowed down
the restoration process. Will the same problem [slow restoration] occur
if there is no BEGIN and END block? I assume the reason for slow inserts
in this instance is that it allows for rollback, if this is the case
can I turn this off?
Thanks in advance
Eric Lam
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: elam@lisasoft.com
Subject: Re: Slow restoration question
In-Reply-To: <444F24E9.2010907@lisasoft.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