Re: Restore of pg_dump taking a long time...

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Ruairi" <rcarroll(at)bluemetrix(dot)com>
Cc: pgsql-admin(at)postgresql(dot)org
Subject: Re: Restore of pg_dump taking a long time...
Date: 2006-05-24 18:47:31
Message-ID: 468.1148496451@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

"Ruairi" <rcarroll(at)bluemetrix(dot)com> writes:
> I'm currently restoring a fairly large DB from a pg_dump and it's taking
> about 12 hours to finish. The main part of this time is spent creating
> indexes. Is there anyway I can speed up the restore process, or do i just
> have to wait?

There's not much you can do to improve the performance of a restore
already in progress. Next time you might want to think about kicking up
maintenance_work_mem before you start it; that's about the only thing
you can really do to speed up index builds.

(Actually, if there are lots of indexes yet to be built, increasing
the setting in postgresql.conf and SIGHUP'ing the postmaster could
be worth doing, as that should affect the builds yet to be done.)

regards, tom lane

In response to

Responses

Browse pgsql-admin by date

  From Date Subject
Next Message mcelroy, tim 2006-05-24 18:56:30 Re: Restore of pg_dump taking a long time...
Previous Message Raphael Bolfing 2006-05-24 13:22:57 tsearch2 (ERROR: Affix parse error at 448 line)