pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Rajesh Kumar Mallah <mallah.rajesh@gmail.com>
To: Jesper Krogh <jesper@krogh.cc>
Cc: pgsql-performance@postgresql.org
Subject: Re: Restore performance?
Date: Mon, 10 Apr 2006 21:38:48 +0530
Message-ID: <a97c77030604100908k61b70b80y9e1f52d3dba10bec@mail.gmail.com> (raw)
In-Reply-To: <443A7FC7.2000001@krogh.cc>
References: <e1d31l$2nt$1@sea.gmane.org>
	<a97c77030604100839p2c4b15c9q88f1258287a0e6d0@mail.gmail.com>
	<443A7FC7.2000001@krogh.cc>

4. fsync can also be turned off while loading huge dataset ,
    but seek others comments  too (as study docs) as i am not sure about the
    reliability. i think it can make a lot of difference.



On 4/10/06, Jesper Krogh <jesper@krogh.cc> wrote:
>
> Rajesh Kumar Mallah wrote:
> >> I'd run pg_dump | gzip > sqldump.gz  on the old system. That took about
> >> 30 hours and gave me an 90GB zipped file. Running
> >> cat sqldump.gz | gunzip | psql
> >> into the 8.1 database seems to take about the same time. Are there
> >> any tricks I can use to speed this dump+restore process up?
> >
> >
> > was the last restore successfull ?
> > if so why do you want to repeat ?
>
> "about the same time" == Estimated guess from restoring a few tables
> I was running a testrun, without disabling updates to the production
> database, the real run is scheduled for easter where there hopefully is
> no users on the system. So I need to repeat, I'm just trying to get a
> feelingabout how long time I need to allocate for the operation.
>
> > 1. run new version of postgres in a different port and pipe pg_dump to
> psql
> > this may save the CPU time of compression , there is no need for a
> temporary
> > dump file.
> >
> > pg_dump | /path/to/psql813  -p 54XX newdb
>
> I'll do that. It is a completely different machine anyway.
>
> > 2. use new version of pg_dump to dump the old database as new version
> >     is supposed to be wiser.
>
> Check.
>
> > 3. make sure you are trapping the restore errors properly
> > psql newdb 2>&1 | cat | tee err works for me.
>
> Thats noted.
>
> --
> Jesper Krogh, jesper@krogh.cc
>
>

view thread (15+ messages)  latest in thread

Message-ID: <a97c77030604100908k61b70b80y9e1f52d3dba10bec@mail.gmail.com>
Permalink:  ../a97c77030604100908k61b70b80y9e1f52d3dba10bec@mail.gmail.com/
Also on:    postgresql.org/message-id/a97c77030604100908k61b70b80y9e1f52d3dba10bec@mail.gmail.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 using the --to and --cc options:
  reply via email

  To: pgsql-performance@postgresql.org
  Cc: mallah.rajesh@gmail.com, jesper@krogh.cc
  Subject: Re: Restore performance?
  In-Reply-To: <a97c77030604100908k61b70b80y9e1f52d3dba10bec@mail.gmail.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