From: | "Rajesh Kumar Mallah" <mallah(dot)rajesh(at)gmail(dot)com> |
---|---|
To: | "Jesper Krogh" <jesper(at)krogh(dot)cc> |
Cc: | pgsql-performance(at)postgresql(dot)org |
Subject: | Re: Restore performance? |
Date: | 2006-04-10 15:39:53 |
Message-ID: | a97c77030604100839p2c4b15c9q88f1258287a0e6d0@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
On 4/10/06, Jesper Krogh <jesper(at)krogh(dot)cc> wrote:
>
> Hi
>
> I'm currently upgrading a Posgresql 7.3.2 database to a
> 8.1.<something-good>
>
> 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 ?
some tips
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
2. use new version of pg_dump to dump the old database as new version
is supposed to be wiser.
3. make sure you are trapping the restore errors properly
psql newdb 2>&1 | cat | tee err works for me.
The database contains quite alot of BLOB, thus the size.
>
> Jesper
> --
> ./Jesper Krogh, jesper(at)krogh(dot)cc, Jabber ID: jesper(at)jabbernet(dot)dk
>
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 6: explain analyze is your friend
>
From | Date | Subject | |
---|---|---|---|
Next Message | Rajesh Kumar Mallah | 2006-04-10 15:42:02 | Re: Restore performance? |
Previous Message | Tom Lane | 2006-04-10 15:35:45 | Re: pg 8.1.3, AIX, huge box, painfully slow. |