From: | Adrian Klaver <adrian(dot)klaver(at)gmail(dot)com> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Cc: | Aleksey Tsalolikhin <atsaloli(dot)tech(at)gmail(dot)com> |
Subject: | Re: database is bigger after dump/restore - why? (60 GB to 109 GB) |
Date: | 2011-02-24 23:48:35 |
Message-ID: | 201102241548.35828.adrian.klaver@gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Thursday, February 24, 2011 3:34:02 pm Aleksey Tsalolikhin wrote:
> 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.
I thought you already had a pg_dump file that you where restoring to the second
db?
>
> Then I will run a pg_dump as text, so I can diff the two files if they are
> different in size.
You don't need to do that if the pg_dump was done using -Fc. You can use
pg_restore to dump a table to a file instead of a database. When it does that
the file will contain a plain text copy. Something like:
pg_restore -a -t really_big_table -f really_big_table_data.sql
Where -a is data only
>
> Thanks!!
> Aleksey
--
Adrian Klaver
adrian(dot)klaver(at)gmail(dot)com
From | Date | Subject | |
---|---|---|---|
Next Message | Adrian Klaver | 2011-02-24 23:52:37 | Re: database is bigger after dump/restore - why? (60 GB to 109 GB) |
Previous Message | Aleksey Tsalolikhin | 2011-02-24 23:38:51 | pg_dump makes our system unusable - any way to pg_dump in the middle of the day? (postgres 8.4.4) |