Received: from sss2.sss.pgh.pa.us (sss.pgh.pa.us [209.114.166.2]) by hub.org (8.9.3/8.9.3) with ESMTP id CAA81473 for ; Tue, 7 Mar 2000 02:14:48 -0500 (EST) (envelope-from tgl@sss.pgh.pa.us) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss2.sss.pgh.pa.us (8.9.3/8.9.3) with ESMTP id CAA19235; Tue, 7 Mar 2000 02:13:57 -0500 (EST) To: Karl Denninger cc: "Ross J. Reedstrom" , zoltan.sebestyen@netvisor.hu, pgsql-sql@postgreSQL.org Subject: Re: [SQL] index file's growing big In-reply-to: <20000306104619.B45015@Denninger.Net> References: <617185BB0AA2D111872400105AD899AD1490D6@netvisorpdc.intranet.netvisor.hu> <20000306102433.B27448@rice.edu> <20000306104619.B45015@Denninger.Net> Comments: In-reply-to Karl Denninger message dated "Mon, 06 Mar 2000 10:46:19 -0600" Date: Tue, 07 Mar 2000 02:13:56 -0500 Message-ID: <19232.952413236@sss.pgh.pa.us> From: Tom Lane Karl Denninger writes: > Further, if the tables are large you want to use "vacuum analyze" to reorder > the indices in a fashion that makes queries more efficient. Just a side comment here: VACUUM ANALYZE has nothing whatever to do with "reordering" indexes. What it does that a plain VACUUM does not do is gather statistics about the table contents (minimum, maximum, and most common value of each column, at present). These stats are then used by the optimizer to make better planning choices. At least we'd like to think they're better, Lord willin' an' the creek don't rise... regards, tom lane