| From: | Vinubalaji Gopal <VGopal(at)abaca(dot)com> |
|---|---|
| To: | Adrian Moisey <adrian(at)careerjunction(dot)co(dot)za>, "pgsql-performance(at)postgresql(dot)org" <pgsql-performance(at)postgresql(dot)org> |
| Subject: | Re: db size |
| Date: | 2008-04-14 06:55:14 |
| Message-ID: | 22E9DC658696E640A074D8B363795BE6228C07ADA5@mail1.ABACA.local |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
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.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Richard Huxton | 2008-04-14 07:14:01 | Re: varchar index joins not working? |
| Previous Message | Adrian Moisey | 2008-04-14 06:29:56 | db size |