Re: copying a database without dumping it

From: Marc Brünink <mbruen(at)smartsoft(dot)de>
To: Tino Wildenhain <tino(at)wildenhain(dot)de>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: copying a database without dumping it
Date: 2005-12-15 11:24:55
Message-ID: 6B09940F-6D5D-11DA-ACBB-000A959A666C@smartsoft.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general


On Donnerstag, Dez 15, 2005, at 12:11 Europe/Berlin, Tino Wildenhain
wrote:

> Marc Brünink schrieb:
>> Hi list,
> ...
>> Now I'l try a custom dump. Perhaps this will suffice. But I guess
>> it's impossible for a dump to be as fast as a cp. So if a cp would
>> be possible I would favour it. Oh, and did I tell: Everything have to
>> be done tommorow..... *sigh*
> Actually its faster. Custom dump is the way to go
> because its much more flexible then dumping plaintext.
[..]
> Since the dump only dumps DDL and Data, its much less
> data then your pg_data directory currently has.

Oh yes! It's damn fast! All hail to the postgres crew! Gosh. My dump
file is just 1.3 GB big. Impressive.
I'm looking forward for the import. Guess I'll get another surprise...

I used:
pg_dump -f shape.postgresql -F c -o -U postgres -Z 9 -v shape

One last thing:
Will I have to re-cluster my tables?

Thanks
Marc

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Андрей 2005-12-15 12:03:15 enable SSL on server
Previous Message Tino Wildenhain 2005-12-15 11:11:52 Re: copying a database without dumping it