Postgres Pro
Downloads
Home   >   mailing lists

Re: database is bigger after dump/restore - why? (60 GB to 109 GB) - Mailing list pgsql-general

From Aleksey Tsalolikhin
Subject Re: database is bigger after dump/restore - why? (60 GB to 109 GB)
Date
Msg-id AANLkTikvs69NceVXiF9jNK_p1oA8DSAb=ZeHBF6=jLT5@mail.gmail.com
Whole thread Raw
In response to Re: database is bigger after dump/restore - why? (60 GB to 109 GB)  (Adrian Klaver <adrian.klaver@gmail.com>)
Responses Re: database is bigger after dump/restore - why? (60 GB to 109 GB)  (Adrian Klaver <adrian.klaver@gmail.com>)
List pgsql-general
Tree view 
Hi.  We're running Postgres 8.4.4 everywhere.

I already have a pg_dump -Fc of the big table from the source, now
I am running a pg_dump -Fc on the recipient, to see if the size is different.

Then I will run a pg_dump as text, so I can diff the two files if they are
different in size.

Thanks!!
Aleksey

pgsql-general by date:

Previous
From: Adrian Klaver
Date:
Subject: Re: database is bigger after dump/restore - why? (60 GB to 109 GB)
Next
From: Aleksey Tsalolikhin
Date:
Subject: pg_dump makes our system unusable - any way to pg_dump in the middle of the day? (postgres 8.4.4)