X-Original-To: pgsql-performance@postgresql.org Received: from localhost (developer.postgresql.org [64.117.224.193]) by developer.postgresql.org (Postfix) with ESMTP id 54AC1925B2B for ; Mon, 2 Jun 2003 09:36:45 -0400 (EDT) Received: from developer.postgresql.org ([64.117.224.193]) by localhost (developer.postgresql.org [64.117.224.193]) (amavisd-new, port 10024) with ESMTP id 88458-06 for ; Mon, 2 Jun 2003 09:36:34 -0400 (EDT) Received: from sss.pgh.pa.us (unknown [192.204.191.242]) by developer.postgresql.org (Postfix) with ESMTP id 84BBC925202 for ; Mon, 2 Jun 2003 09:36:34 -0400 (EDT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.12.9/8.12.9) with ESMTP id h52DaWU6007851; Mon, 2 Jun 2003 09:36:32 -0400 (EDT) To: "Mindaugas Riauba" Cc: pgsql-performance@postgresql.org Subject: Re: Degrading performance In-reply-to: <005a01c328c8$885b9760$f20214ac@bite.lt> References: <005a01c328c8$885b9760$f20214ac@bite.lt> Comments: In-reply-to "Mindaugas Riauba" message dated "Mon, 02 Jun 2003 08:33:38 +0300" Date: Mon, 02 Jun 2003 09:36:31 -0400 Message-ID: <7850.1054560991@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: by amavisd-new X-Archive-Number: 200306/12 X-Sequence-Number: 2096 "Mindaugas Riauba" 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