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 KAA88375 for ; Thu, 25 May 2000 10:39:32 -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 KAA22562; Thu, 25 May 2000 10:39:09 -0400 (EDT) To: "Hiroshi Inoue" cc: "Ryan Bradetich" , pgsql-sql@postgresql.org Subject: Re: Use of index in 7.0 vs 6.5 In-reply-to: <000e01bfc619$9fa5f9c0$2801007e@tpf.co.jp> References: <000e01bfc619$9fa5f9c0$2801007e@tpf.co.jp> Comments: In-reply-to "Hiroshi Inoue" message dated "Thu, 25 May 2000 16:19:54 +0900" Date: Thu, 25 May 2000 10:39:09 -0400 Message-ID: <22559.959265549@sss.pgh.pa.us> From: Tom Lane X-Archive-Number: 200005/140 "Hiroshi Inoue" writes: >> One way to put a thumb on the scales is to reduce the value of the SET >> variable random_page_cost. The default value is 4.0, which seems to >> correspond more or less to reality, but reducing it to 3 or so would >> shift the planner pretty nicely in the direction of indexscans. > Or how about changing current fudge factor ? > For example,from 0.5 to 0.2 which is the fudge factor of attdisbursion > calculation. Yes, that's another way --- and probably more defensible than changing random_page_cost, now that I think about it. Unfortunately it's a hardwired constant and so not as easily experimented with :-(. regards, tom lane