Re: dbsize & pg_dump - Mailing list pgsql-admin

From Jim C. Nasby
Subject Re: dbsize & pg_dump
Date
Msg-id 20060426224732.GF97354@pervasive.com
Whole thread Raw
In response to Re: dbsize & pg_dump  ("Jason Minion" <jason.minion@sigler.com>)
List pgsql-admin
On Tue, Apr 25, 2006 at 04:47:53PM -0500, Jason Minion wrote:
> Usually a dump is significantly smaller than a live database due to
> space taken up by indexes and discarded tuples from MVCC. If it's
> significantly smaller you may also want to take a look at your vacuuming
> procedure.

Between excluding the database overhead (mostly tuple headers),
excluding indexes, and compression, getting a 10x reduction in database
size isn't unexpected. Using pg_dumpall and bzip2 the databases on
http://stats.distributed.net go from 41G down to 2G.
--
Jim C. Nasby, Sr. Engineering Consultant      jnasby@pervasive.com
Pervasive Software      http://pervasive.com    work: 512-231-6117
vcard: http://jim.nasby.net/pervasive.vcf       cell: 512-569-9461

pgsql-admin by date:

Previous
From: Warren Little
Date:
Subject: need a bit of help
Next
From: "Jim C. Nasby"
Date:
Subject: Re: Tale partitioning