From: | "Nicola Mauri" <Nicola(dot)Mauri(at)saga(dot)it> |
---|---|
To: | pgsql-admin(at)postgresql(dot)org |
Subject: | Dump size bigger than pgdata size? |
Date: | 2006-06-21 14:30:17 |
Message-ID: | OF406B6E88.F5B37D76-ONC1257194.004D5FAC-C1257194.004F9F44@saga.it |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
[sorry if this was previously asked: list searches seem to be down]
I'm using pg_dump to take a full backup of my database using a compressed
format:
$ pg_dump -Fc my_db > /backup/my_db.dmp
It produces a 6 GB file whereas the pgdata uses only 5 GB of disk space:
$ ls -l /backup
-rw-r--r-- 6592715242 my_db.dmp
$ du -b /data
5372269196 /data
How could it be?
As far as I know, dumps should be smaller than filesystem datafile since
they do not store indexes, etc.
Database contains about one-hundred-thousands binary images, some of which
may be already compressed. So i tried the --compress=0 option but this
produces a dump that does not fit on my disk (more than 11 GB).
I'm using postgres 8.1.2 on RHEL4.
So, what can I do to diagnose the problem?
Thanks in advance,
Nicola
From | Date | Subject | |
---|---|---|---|
Next Message | Aaron Bono | 2006-06-21 14:30:30 | Re: Unique constraint and index-combination feature in 8.1 |
Previous Message | Thusitha Kodikara | 2006-06-21 10:57:43 | Re: "UNICODE" error during restoration |