X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (mx1.hub.org [200.46.208.251]) by postgresql.org (Postfix) with ESMTP id D31169F94EA for ; Wed, 24 May 2006 15:47:46 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.208.251]) (amavisd-new, port 10024) with ESMTP id 18251-07 for ; Wed, 24 May 2006 15:47:37 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey- Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by postgresql.org (Postfix) with ESMTP id 2CC779F9398 for ; Wed, 24 May 2006 15:47:36 -0300 (ADT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.13.6/8.13.6) with ESMTP id k4OIlV5t000470; Wed, 24 May 2006 14:47:31 -0400 (EDT) To: "Ruairi" cc: pgsql-admin@postgresql.org Subject: Re: Restore of pg_dump taking a long time... In-reply-to: <008c01c67f26$9848caf0$2815a8c0@D5T7W62J> References: <008c01c67f26$9848caf0$2815a8c0@D5T7W62J> Comments: In-reply-to "Ruairi" message dated "Wed, 24 May 2006 12:38:33 +0100" Date: Wed, 24 May 2006 14:47:31 -0400 Message-ID: <468.1148496451@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200605/338 X-Sequence-Number: 21870 "Ruairi" 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