pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Naomi Walker <nwalker@eldocomp.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Ruairi <rcarroll@bluemetrix.com>
Cc: pgsql-admin@postgresql.org <pgsql-admin@postgresql.org>
Subject: Re: Restore of pg_dump taking a long time...
Date: Wed, 24 May 2006 13:05:04 -0700
Message-ID: <4474BC70.6080402@eldocomp.com> (raw)

I would typically drop the indicies before taking the dump, and recreate
in the new instance.  I know the loads go alot faster that way.  Perhaps
the index creation would be the same.

Tom Lane wrote:
> "Ruairi" <rcarroll@bluemetrix.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
> 
> ---------------------------(end of broadcast)---------------------------
> TIP 2: Don't 'kill -9' the postmaster


-- 
----------------------------------------------------------------------------
Naomi Walker                          Chief Information Officer
Eldorado Computing, Inc.              nwalker@eldocomp.com 602-604-3100
----------------------------------------------------------------------------
What lies behind us and what lies before us are tiny matters compared to
what lies within us.     - William Morrow
----------------------------------------------------------------------------

-- CONFIDENTIALITY NOTICE --

Information transmitted by thisĀ e-mail is proprietary to MphasiS and/or its Customers and is intended for use only by the individual or entity to which it is addressed, and may contain information that isĀ privileged, confidential or exempt from disclosure under applicable law. If you are not the intended recipient or it appears that this mail has been forwarded to you without proper authority, you are notified that any use or dissemination of this information in any manner is strictly prohibited. In such cases, please notify us immediately at mailmaster@mphasis.com and delete this mail from your records.



view thread (9+ messages)  latest in thread

Message-ID: <4474BC70.6080402@eldocomp.com>
Permalink:  ../4474BC70.6080402@eldocomp.com/
Also on:    postgresql.org/message-id/4474BC70.6080402@eldocomp.com

 · 

reply

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 from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-admin@postgresql.org
  Cc: nwalker@eldocomp.com, tgl@sss.pgh.pa.us, rcarroll@bluemetrix.com
  Subject: Re: Restore of pg_dump taking a long time...
  In-Reply-To: <4474BC70.6080402@eldocomp.com>
  References: <4474BC70.6080402@eldocomp.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