> The standard form of VACUUM is best used with the goal of maintaining a fairly level steady-state usage of disk space. The standard form finds old tuples and makes their space available for re-use within the table, but it does not try very hard to shorten the table file and return disk space to the operating system. If you need to return disk space to the operating system you can use VACUUM FULL --- but what’s the point of releasing disk space that will only have to be allocated again soon? Moderately frequent standard VACUUMs are a better approach than infrequent VACUUM FULLs for maintaining heavily-updated tables. > > Recommended practice for most sites is to schedule a database-wide VACUUM once a day at a lowusage time of day, supplemented by more frequent vacuuming of heavily-updated tables if necessary. (If you have multiple databases in an installation, don’t forget to vacuum each one; the vacuumdb script may be helpful.) Use plain VACUUM, not VACUUM FULL, for routine vacuuming for space recovery.
So does VACUUM require the database to be taken offline? Or was this an issue with older versions of pgSQL? As I don't see the Geocrawler under maintainence pages nowadays. There was a time when I only saw the under maintainence page at Geocrawler!! Ambar Roy _______________________________________________ ilugd mailing list [EMAIL PROTECTED] http://frodo.hserus.net/mailman/listinfo/ilugd
