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 7DBB89258E4 for ; Mon, 2 Jun 2003 13:26:18 -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 39050-02 for ; Mon, 2 Jun 2003 13:26:06 -0400 (EDT) Received: from sss.pgh.pa.us (unknown [192.204.191.242]) by developer.postgresql.org (Postfix) with ESMTP id 344AF92644E for ; Mon, 2 Jun 2003 13:25:42 -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 h52HPNU6009539; Mon, 2 Jun 2003 13:25:23 -0400 (EDT) To: "scott.marlowe" Cc: Mindaugas Riauba , pgsql-performance@postgresql.org Subject: Re: Degrading performance In-reply-to: References: Comments: In-reply-to "scott.marlowe" message dated "Mon, 02 Jun 2003 10:34:43 -0600" Date: Mon, 02 Jun 2003 13:25:22 -0400 Message-ID: <9538.1054574722@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: by amavisd-new X-Archive-Number: 200306/16 X-Sequence-Number: 2100 "scott.marlowe" writes: > On Mon, 2 Jun 2003, Tom Lane wrote: >>> 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. The table's not very big though. As long as he keeps after it with sufficiently-frequent vacuuming, it won't need much FSM space. regards, tom lane