On Mon, 2 Jun 2003, Tom Lane wrote:
> "Mindaugas Riauba" <mind@bi.lt> writes:
> > I have table with slowly degrading performance. Table is special is
> > such way that all its rows are updated every 5 minutes (routers interfaces).
> > vacuum does not help. vacuum full does but I'd like to avoid it.
>
> VACUUM will do the trick, you just need to do it every five minutes or
> so. I suggest a cron job to vacuum just the one table.
>
> > INFO: Rel ifdata: Pages: 4887 --> 17; Tuple(s) moved: 776.
> > CPU 0.30s/0.35u sec elapsed 1.65 sec.
>
> That says you waited way too long to vacuum --- over two hundred update
> cycles, evidently.
Don't forget to crank up your fsm settings in $PGDATA/postgresql.conf as
well.
