From: Vivek Khera <khera@kcilink.com>
To: pgsql-performance@postgresql.org
Subject: Re: pg_restore taking 4 hours!
Date: Mon, 13 Dec 2004 11:37:28 -0500
Message-ID: <x73byab1dj.fsf@yertle.int.kciLink.com> (raw)
References: <41ADA82A.7070405@carvalhaes.net>
>>>>> "RC" == Rodrigo Carvalhaes <grupos@carvalhaes.net> writes:
RC> Hi!
RC> I am using PostgreSQL with a proprietary ERP software in Brazil. The
RC> database have around 1.600 tables (each one with +/- 50 columns).
RC> My problem now is the time that takes to restore a dump. My customer
RC> database have arount 500mb (on the disk, not the dump file) and I am
RC> making the dump with pg_dump -Fc, my dumped file have 30mb. To make
RC> the dump, it's taking +/- 1,5 hours BUT to restore (using pg_restore )
RC> it it takes 4 - 5 hours!!!
I regularly dump a db that is compressed at over 2Gb. Last time I did
a restore on the production box it took about 3 hours. Restoring it
into a development box with a SATA RAID0 config takes like 7 hours or
so.
The biggest improvement in speed to restore time I have discovered is
to increase the checkpoint segments. I bump mine to about 50. And
moving the pg_xlog to a separate physical disk helps a lot there, too.
--
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Vivek Khera, Ph.D. Khera Communications, Inc.
Internet: khera@kciLink.com Rockville, MD +1-301-869-4449 x806
AIM: vivekkhera Y!: vivek_khera http://www.khera.org/~vivek/
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: khera@kcilink.com
Subject: Re: pg_restore taking 4 hours!
In-Reply-To: <x73byab1dj.fsf@yertle.int.kciLink.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