Re: Degrading performance

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Mindaugas Riauba" <mind(at)bi(dot)lt>
Cc: pgsql-performance(at)postgresql(dot)org
Subject: Re: Degrading performance
Date: 2003-06-02 13:36:31
Message-ID: 7850.1054560991@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

"Mindaugas Riauba" <mind(at)bi(dot)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.

regards, tom lane

In response to

Responses

Browse pgsql-performance by date

  From Date Subject
Next Message scott.marlowe 2003-06-02 15:20:28 Re: Enabling and Disabling Sequencial Scan
Previous Message Peter Childs 2003-06-02 07:51:49 Re: Index speeds up one row table (why)?