On Jun 18, 2006, at 10:47 PM, Qingqing Zhou wrote:
""Linux Portal"" <[EMAIL PROTECTED]> wrote
The article on the subject can be read here:
http://linux.inet.hr/optimize_postgresql_database_size.html
After dump/restore the database size is 1685 MB and after
vacuum-full/reindex is 1990 MB. Where we saved 305 MB?
My guess would be due to toasted text columns... does VACUUM FULL
know to vacuum the toast tables only after committing the vacuum on
the base heap?
--
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
