Robert Treat <rtreat@webmd.net> writes:
> For the record, we went through this procedure about 2 weeks ago (slow
> queries, reindex, vacuum, drop/reload) So I am wondering what might be
> causing the table to grow so large. We run a function against the table
> about every 5 minutes which updates on average maybe 100 rows and adds
> rows at the rate of maybe 1 an hour, but otherwise everything else is
> selects. I wouldn't think that continual updates would have such a
> adverse effect on table size, and even if so shouldn't vacuum take care
> of this?
You can do VACUUM FULL if you want to re-shrink the table. If you want
to stick with plain VACUUMs then you need to do them often enough to
keep the table size reasonable. You didn't say what your maintenance
schedule is...
If your overall database is large then you might need to increase the
size of the free space map (see postgresql.conf).
regards, tom lane