by VGopal@[EMAIL PROTECTED]
(Vinubalaji Gopal)
Apr 13, 2008 at 11:55 PM
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=3Dformat
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
mos=
t flexible format in that it allows reordering of data load as well as
sche=
ma elements. This format is also compressed by default.
"
The output is compressed and it is a dump of the database which contain
th=
e 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
da=
tabase by reclaiming any unused space and you can use the filesystem based
=
backup or backup/restore strategy.
--=20
Sent via pgsql-performance mailing list (pgsql-performance@[EMAIL PROTECTED]
)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-performance
