Received: from wallace.ece.rice.edu (root@wallace.ece.rice.edu [128.42.12.154]) by hub.org (8.9.3/8.9.3) with ESMTP id NAA62692 for ; Mon, 6 Mar 2000 13:03:15 -0500 (EST) (envelope-from reedstrm@wallace.ece.rice.edu) Received: by wallace.ece.rice.edu via sendmail from stdin id (Debian Smail3.2.0.102) for pgsql-sql@postgresql.org; Mon, 6 Mar 2000 12:02:22 -0600 (CST) Date: Mon, 6 Mar 2000 12:02:22 -0600 From: "Ross J. Reedstrom" To: Karl Denninger Cc: zoltan.sebestyen@netvisor.hu, pgsql-sql@postgresql.org Subject: Re: [SQL] index file's growing big Message-ID: <20000306120222.A28212@rice.edu> References: <617185BB0AA2D111872400105AD899AD1490D6@netvisorpdc.intranet.netvisor.hu> <20000306102433.B27448@rice.edu> <20000306104619.B45015@Denninger.Net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii User-Agent: Mutt/1.0i In-Reply-To: <20000306104619.B45015@Denninger.Net>; from karl@Denninger.Net on Mon, Mar 06, 2000 at 10:46:19AM -0600 On Mon, Mar 06, 2000 at 10:46:19AM -0600, Karl Denninger wrote: > Uh, why not just "vacuum" the table? > > You want to do this periodically anyway, as Postgres does not re-use TABLE > entries either, and the table file itself will grow without bound if you > don't do this once in a while. > > Further, if the tables are large you want to use "vacuum analyze" to reorder > the indices in a fashion that makes queries more efficient. > Well, with a recent version, that will help keep the index from growing as fast, but it will still grow. That's the point of my garbled description. However, if Zoltan is _not_ vacuuming regularly, that's a problem as well. If he wasn't, though, I'd have expected him to complain about the size of the table file, not the index file. Ross -- Ross J. Reedstrom, Ph.D., NSBRI Research Scientist/Programmer Computer and Information Technology Institute Rice University, 6100 S. Main St., Houston, TX 77005