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 MAA72607 for ; Thu, 25 May 2000 12:04:20 -0400 (EDT) (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 MAA23048; Thu, 25 May 2000 12:03:48 -0400 (EDT) To: Bruce Momjian cc: "Mikheev, Vadim" , "'Hiroshi Inoue'" , Ryan Bradetich , pgsql-sql@postgresql.org Subject: Re: Use of index in 7.0 vs 6.5 In-reply-to: <200005251511.LAA21178@candle.pha.pa.us> References: <200005251511.LAA21178@candle.pha.pa.us> Comments: In-reply-to Bruce Momjian message dated "Thu, 25 May 2000 11:11:23 -0400" Date: Thu, 25 May 2000 12:03:48 -0400 Message-ID: <23045.959270628@sss.pgh.pa.us> From: Tom Lane X-Archive-Number: 200005/143 Bruce Momjian writes: > That certainly would make sense. We have hesitated to gather more > statistics because of the time involved. Fuller statistics on just the > indexed columns could be a big win and be done fairly quickly because > the rows are already sorted in the index. Yeah, a scan over just the index itself would be a perfect way to gather stats. The normal objection to it (can't tell whether entries correspond to currently-valid tuples) doesn't apply, because we don't really care whether the stats are perfectly accurate. Should put this in TODO, along with something about splitting the ANALYZE function out of VACUUM and making it invokable as a separate statement. regards, tom lane