> You'll still need to VACUUM to get rid of the obsoleted versions of the
> row. The point of the planned 7.2 changes is to make VACUUM cheap and
> nonintrusive enough so that you can run it frequently on tables that are
> seeing continual updates.
If it becomes non-intrusive, then why not have PostgreSQL run VACUUM
automatically when certain conditions (user-configurable, load, changes per
table, etc.) are met.
All the sys admin would need to do is put the VACCUUM FULL in a cron job.
Chris
---------------------------(end of broadcast)---------------------------
TIP 4: Don't 'kill -9' the postmaster
