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 [EMAIL PROTECTED] Pervasive Software http://pervasive.com work: 512-231-6117 vcard: http://jim.nasby.net/pervasive.vcf cell: 512-569-9461 ---------------------------(end of broadcast)--------------------------- TIP 9: In versions below 8.0, the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match
