Thread: pgsql: Add a fudge factor to genericcostestimate() to prevent the

pgsql: Add a fudge factor to genericcostestimate() to prevent the

From

tgl@postgresql.org (Tom Lane)

Date:

24 July 2006, 01:19:52

Log Message:
-----------
Add a fudge factor to genericcostestimate() to prevent the planner from
thinking that indexes of different sizes are equally attractive.  Per
gripe from Jim Nasby.  (I remain unconvinced that there's such a problem
in existing releases, but CVS HEAD definitely has got a problem because
of its new count-only-leaf-pages approach to indexscan costing.)

Modified Files:
--------------
    pgsql/src/backend/utils/adt:
        selfuncs.c (r1.209 -> r1.210)
        (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/utils/adt/selfuncs.c.diff?r1=1.209&r2=1.210)