Slow restoration question - Mailing list pgsql-performance

From Eric Lam
Subject Slow restoration question
Date
Msg-id 444F24E9.2010907@lisasoft.com
Whole thread Raw
Responses Re: Slow restoration question  (Tom Lane <tgl@sss.pgh.pa.us>)
Re: Slow restoration question  ("Jim C. Nasby" <jnasby@pervasive.com>)
List pgsql-performance
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

pgsql-performance by date:

Previous
From: "mlartz@gmail.com"
Date:
Subject: Re: Hardware: HP StorageWorks MSA 1500
Next
From: "Bert"
Date:
Subject: Re: Easy question