"Hiroshi Inoue" <[EMAIL PROTECTED]> 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
- [SQL] Use of index in 7.0 vs 6.5 Ryan Bradetich
- Re: [SQL] Use of index in 7.0 vs 6.5 Tom Lane
- Re: [SQL] Use of index in 7.0 vs 6.5 Ryan Bradetich
- Re: [SQL] Use of index in 7.0 vs 6.5 Tom Lane
- RE: [SQL] Use of index in 7.0 vs 6.5 Hiroshi Inoue
- Re: [SQL] Use of index in 7.0 vs 6.5 Tom Lane
- Re: [SQL] Use of index in 7.0 vs 6.5 Ryan Bradetich
- Re: [SQL] Use of index in 7.0 vs 6.5 Tom Lane
- Re: [SQL] Use of index in 7.0 vs ... Ryan Bradetich
- Re: [SQL] Use of index in 7.0 vs 6.5 Jeff Hoffmann
- Re: [SQL] Use of index in 7.0 vs 6.5 Tom Lane
- RE: [SQL] Use of index in 7.0 vs 6.5 Mikheev, Vadim
- Re: [SQL] Use of index in 7.0 vs 6.5 Bruce Momjian
- Re: [SQL] Use of index in 7.0 vs 6.5 Tom Lane
- Re: [SQL] Use of index in 7.0 vs 6.5 Bruce Momjian
- RE: [SQL] Use of index in 7.0 vs 6.5 Hiroshi Inoue