pgsql: Improve usage of effective_cache_size parameter by assuming that

Поиск
Список
Период
Сортировка
От tgl@postgresql.org (Tom Lane)
Тема pgsql: Improve usage of effective_cache_size parameter by assuming that
Дата
Msg-id 20060919224953.E86929FA433@postgresql.org
обсуждение исходный текст
Список pgsql-committers
Log Message:
-----------
Improve usage of effective_cache_size parameter by assuming that all the
tables in the query compete for cache space, not just the one we are
currently costing an indexscan for.  This seems more realistic, and it
definitely will help in examples recently exhibited by Stefan
Kaltenbrunner.  To get the total size of all the tables involved, we must
tweak the handling of 'append relations' a bit --- formerly we looked up
information about the child tables on-the-fly during set_append_rel_pathlist,
but it needs to be done before we start doing any cost estimation, so
push it into the add_base_rels_to_query scan.

Modified Files:
--------------
    pgsql/src/backend/nodes:
        outfuncs.c (r1.284 -> r1.285)
        (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/nodes/outfuncs.c.diff?r1=1.284&r2=1.285)
    pgsql/src/backend/optimizer/path:
        allpaths.c (r1.152 -> r1.153)
        (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/optimizer/path/allpaths.c.diff?r1=1.152&r2=1.153)
        costsize.c (r1.165 -> r1.166)
        (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/optimizer/path/costsize.c.diff?r1=1.165&r2=1.166)
    pgsql/src/backend/optimizer/plan:
        initsplan.c (r1.121 -> r1.122)

(http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/optimizer/plan/initsplan.c.diff?r1=1.121&r2=1.122)
        planmain.c (r1.95 -> r1.96)
        (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/optimizer/plan/planmain.c.diff?r1=1.95&r2=1.96)
    pgsql/src/backend/optimizer/util:
        plancat.c (r1.125 -> r1.126)
        (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/optimizer/util/plancat.c.diff?r1=1.125&r2=1.126)
        relnode.c (r1.81 -> r1.82)
        (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/optimizer/util/relnode.c.diff?r1=1.81&r2=1.82)
    pgsql/src/backend/utils/adt:
        selfuncs.c (r1.211 -> r1.212)
        (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/utils/adt/selfuncs.c.diff?r1=1.211&r2=1.212)
    pgsql/src/include/nodes:
        relation.h (r1.126 -> r1.127)
        (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/include/nodes/relation.h.diff?r1=1.126&r2=1.127)
    pgsql/src/include/optimizer:
        cost.h (r1.79 -> r1.80)
        (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/include/optimizer/cost.h.diff?r1=1.79&r2=1.80)
        plancat.h (r1.40 -> r1.41)
        (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/include/optimizer/plancat.h.diff?r1=1.40&r2=1.41)

В списке pgsql-committers по дате отправления:

Предыдущее
От: neilc@postgresql.org (Neil Conway)
Дата:
Сообщение: pgsql: Do a round of copy-editing for the release notes: fix some typos
Следующее
От: neilc@postgresql.org (Neil Conway)
Дата:
Сообщение: pgsql: Improvements to the partitioning documentation.