Received: from localhost.localdomain (postgresql.org [64.49.215.8]) by localhost (Postfix) with ESMTP id 5925B476419 for ; Fri, 10 May 2002 22:05:00 -0400 (EDT) Received: from sss.pgh.pa.us (unknown [192.204.191.242]) by postgresql.org (Postfix) with ESMTP id 6C851475E5D for ; Fri, 10 May 2002 22:04:59 -0400 (EDT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.11.4/8.11.4) with ESMTP id g4B24rW10111; Fri, 10 May 2002 22:04:53 -0400 (EDT) To: Brian McCane Cc: pgsql-admin Subject: Re: VACUUM FULL In-reply-to: <20020510185436.F62674-100000@fw.mccons.net> References: <20020510185436.F62674-100000@fw.mccons.net> Comments: In-reply-to Brian McCane message dated "Fri, 10 May 2002 19:18:42 -0500" Date: Fri, 10 May 2002 22:04:53 -0400 Message-ID: <10108.1021082693@sss.pgh.pa.us> From: Tom Lane X-Archive-Number: 200205/93 X-Sequence-Number: 4268 Brian McCane writes: > I INSERT/UPDATE/DELETE approximately 300,000 records per day, but this > number is increasing on a daily basis as I make changes which improve the > performance of my data gathering tools (spiders ;). Two days ago, it had > reached the point where a search for a 3-word term (ie. free news servers) > took about 60 seconds. I have just spent 48 hours running a VACUUM FULL > on my table, and now the same search takes < 10 seconds. I would have to assume that the change is due to a change in plan, and not directly due to VACUUM having compacted out a small part of the space. Did you do VACUUM ANALYZE, or just plain VACUUM? When was the last time you did VACUUM (or ANALYZE) on this table? What plan is being used now? Do you have any idea what plan was used before? regards, tom lane