From: Ryan Bradetich <ryan_bradetich@hp.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Hiroshi Inoue <Inoue@tpf.co.jp>
Cc: pgsql-sql@postgresql.org
Subject: Re: Use of index in 7.0 vs 6.5
Date: Thu, 25 May 2000 17:40:35 -0600
Message-ID: <392DB9F3.2907B731@hp.com> (raw)
References: <000e01bfc619$9fa5f9c0$2801007e@tpf.co.jp>
<22559.959265549@sss.pgh.pa.us>
Tom Lane wrote:
> "Hiroshi Inoue" <Inoue@tpf.co.jp> 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.
This worked great! Is their a place I can change the default to 3?
I do not want to change all the scripts to include this :)
> > 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
Can you give me more information about this? I do not have a problem
re-compiling the database and performing more testing if you would like.
Tom,
To answer your question in a previous post:
Since you find that in reality the indexscan method is very quick,
I'm guessing that there are actually fairly few tuples matching
host_id = 404. Could you run a quick "select count(*)" to check?
procman=# select count(*) from medusa where host_id = 404;
count
-------
680
(1 row)
procman=# select count(catagory) from medusa where host_id = 404 and
catagory like 'A%';
count
-------
4
(1 row)
Thanks again everyone for all the help! Now that I am finished with school
for the semester,
I should have time to make contributions again ... :)
Ryan
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-sql@postgresql.org
Cc: ryan_bradetich@hp.com, tgl@sss.pgh.pa.us, Inoue@tpf.co.jp
Subject: Re: Use of index in 7.0 vs 6.5
In-Reply-To: <392DB9F3.2907B731@hp.com>
References: <000e01bfc619$9fa5f9c0$2801007e@tpf.co.jp> <22559.959265549@sss.pgh.pa.us> <392DB9F3.2907B731@hp.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox