pgsql: Add a fudge factor to genericcostestimate() to prevent the - Mailing list pgsql-committers

From tgl@postgresql.org (Tom Lane)
Subject pgsql: Add a fudge factor to genericcostestimate() to prevent the
Date
Msg-id 20060724011948.7B7689FA61D@postgresql.org
Whole thread Raw
List pgsql-committers
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)

pgsql-committers by date:

Previous
From: tgl@postgresql.org (Tom Lane)
Date:
Subject: pgsql: Convert the lock manager to use the new dynahash.c support for
Next
From: adunstan@postgresql.org (Andrew Dunstan)
Date:
Subject: pgsql: Remove dubious and redundant (we think) setting of libdir in PATH