<p>To whom it may concern,<p>I am a java developer using postgres as a DB server. Me and my development team have a
productcomprised of about 50 tables, with about 10,000 records in the largest table. We have looked for concrete
answersin books and the web for solutions to several problems that are plaguing us. Now we look to the source.<p>Issue
#1Massive deletion of records.<p>Q - If many (eg hundreds) records are deleted (purposely), those records get flagged
forlater removal. What is the best sequence of operations to optimize the database afterwards? Is it Vacuum,
Re-index,then do a Vacuum Analyze.<p>Some of what I have read suggests that doing a vacuum without a re-index, can
causea given index to be invalid (ie entries pointing to records that do not match the index criteria).<p>This would
thensuggest that doing a Vacuum Analyze would create an incorrect statistics table.<p>Any help regarding the best
maintenancepolicy, ramifications of mass deletions, vacuuming, and re-indexing would be most appreciated. Thanks<p><br
/><hrsize="1" />Do you Yahoo!?<br /><a href="http://rd.yahoo.com/hosting/mailsig/*http://webhosting.yahoo.com">Yahoo!
WebHosting</a> - Let the expert host your site
