Re: Fastest DB restore options

From: "Ben Trewern" <ben(dot)trewern(at)mowlem(dot)com>
To: pgsql-admin(at)postgresql(dot)org
Subject: Re: Fastest DB restore options
Date: 2007-02-25 22:58:15
Message-ID: ert4ab$14if$1@news.hub.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

If you are just looking for the least down time between stopping one server
and starting the new one you could try Slony see
http://gborg.postgresql.org/project/slony1/projdisplay.php

Regards,

Ben

<ogjunk-pgjedan(at)yahoo(dot)com> wrote in message
news:821429(dot)69798(dot)qm(at)web50304(dot)mail(dot)yahoo(dot)com(dot)(dot)(dot)
> Hello,
>
> I have a fairly large DB to dump and restore as fast as possible. I'm
> moving from 8.0.3 to 8.2.3! :)
>
> I normally dump with these options:
>
> -d MyDB --clean --inserts --column-inserts --format=P
>
> But the last time I tried that, the restore took foreeeeeeeeeeeeeever. So
> I'm looking for the fastest way to import data from the old DB to the new
> one. Judging from pg_dump man page the following should be the fastest
> dump & restore:
>
> -d MyDB --format=c --ignore-version
>
> Is there anything else I can do to make the restore as fast as possible?
>
> Thanks,
> Otis
>
> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
> Simpy -- http://www.simpy.com/ - Tag - Search - Share
>
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 9: In versions below 8.0, the planner will ignore your desire to
> choose an index scan if your joining column's datatypes do not
> match
>

In response to

Browse pgsql-admin by date

  From Date Subject
Next Message ashok@kalculate.com 2007-02-26 05:44:06 invalid page header in block 428 of relation "pg_attribute"
Previous Message Mike 2007-02-25 01:41:15 Re: Lost password...