[PERFORM] db size

[Adrian Moisey]

Hi

We currently have a 16CPU 32GB box running postgres 8.2.

When I do a pg_dump with the following parameters "/usr/bin/pg_dump -E 
UTF8 -F c -b" I get a file of 14GB in size.


But the database is 110GB in size on the disk.  Why the big difference 
in size?  Does this have anything to do with performance?


--
Adrian Moisey
Systems Administrator | CareerJunction | Your Future Starts Here.
Web: www.careerjunction.co.za | Email: [EMAIL PROTECTED]
Phone: +27 21 686 6820 | Mobile: +27 82 858 7830 | Fax: +27 21 686 6842

--
Sent via pgsql-performance mailing list (pgsql-performance@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-performance

Re: [PERFORM] db size

[Vinubalaji Gopal]

Hi Adrian,



>When I do a pg_dump with the following parameters "/usr/bin/pg_dump -E
UTF8 -F c -b" I get a file of 14GB in size.


>From the man page of pg_dump
"
-F format, --format=format

 Selects the format of the output. format can be one of the following:
c
output a custom archive suitable for input into pg_restore. This is the most 
flexible format in that it allows reordering of data load as well as schema 
elements. This format is also compressed by default.
"

 The output is compressed and it is a dump of the database which contain the 
SQL commands:



>But the database is 110GB in size on the disk.  Why the big difference
>in size?  Does this have anything to do with performance?

VACUUM or VACUUM FULL of the entire database will reduce the size of the 
database by reclaiming any unused space and you can use the filesystem based 
backup or backup/restore strategy.

-- 
Sent via pgsql-performance mailing list (pgsql-performance@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-performance