Re: pg_restore problem

From: Robert Treat <xzilla(at)users(dot)sourceforge(dot)net>
To: lists <lists(at)insyde(dot)com(dot)br>
Cc: pgsql-admin(at)postgresql(dot)org
Subject: Re: pg_restore problem
Date: 2003-03-31 13:43:16
Message-ID: 1049118197.13798.1712.camel@camel
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

Are you sure your restoring to an empty database? If you try to restore
your dump into the database you dumped it from (without first
drop/create) it will take forever as you'll have all kinds of data
collisions (imagine every insert into a table erroring out due to
duplicate primary key).

As for the -Ft vs. -Fc size question, the tar format is not a compressed
format, while the "c"ustom format is.

Robert Treat

On Fri, 2003-03-28 at 07:35, lists wrote:
> Hi,
>
> I've a dump I made with the command:
>
> pg_dump -a -b -Fc -f DB.dump -o -v DB
>
> then I try to restore with:
>
> pg_restore -a -d DB2 -Fc -o -v DB.dump
>
> This database is about 1.5Gb big.
>
> The dump takes abou 1 hour, but the restore takes forever!
>
> Last time I ran it, it takes more than 10 hours, when I gave up
> and stopped the process.
>
> Tried with both Ft and Fc.
>
> Another doubt: Why a dump of this DB with Ft has about the
> same size of the original DB(1.5GB) and with Fc it has about 50MB?
>
> My system is:
> P3 1Ghz, 1GB ram, Win2k, Postgres 7.2.2
> Free space ~5GB.
>
> TIA,
>
> Ricardo.

In response to

Responses

Browse pgsql-admin by date

  From Date Subject
Next Message Robert Treat 2003-03-31 14:01:50 Re: Realistic upper bounds on table size
Previous Message Robert Treat 2003-03-31 13:38:36 Re: Requests per second ?