[postgis-users] Got VACUUM reccomendation in newly-created postGIStable

[Gregory Williamson]

Per-Olof wrote:
> 
> kreshna_iceheart at yahoo.com skrev:
> >  And if I run
> > VACUUM ANALYZE, there won't be anything bad happen,
> >   
> nope, do It!
> Seriously, this is exactly the correct way to go.
> vacuum analyze updates the index statistics.
> 

Nit-picking department chimes in:

 ANALYZE updates statistics for indexed columns

 VACUUM cleans out dead tuples from deletes & updates and prevents table bloat and transaction id wraparound failure.

So ANALYZE (which is fast and relatively light-weight) whenever data distributions change

and

VACUUM periodically for the whole database, and vacuum tables that have updates and deletes. Or use autovacuum if you on a recent release of PostgreSQL (8.2 seems fairly robust but your experience may differ on what sort of processing you do).

HTH,

Greg Williamson
Senior DBA
GlobeXplorer LLC, a DigitalGlobe company

Confidentiality Notice: This e-mail message, including any attachments, is for the sole use of the intended recipient(s) and may contain confidential and privileged information and must be protected in accordance with those provisions. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message.

(My corporate masters made me say this.)
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/postgis-users/attachments/20071129/254f7ba8/attachment.html>