pgsql: Adjust nodeBitmapIndexscan to keep the target index opened from

Поиск
Список
Период
Сортировка
От tgl@svr1.postgresql.org (Tom Lane)
Тема pgsql: Adjust nodeBitmapIndexscan to keep the target index opened from
Дата
Msg-id 20050505033723.C216B52A37@svr1.postgresql.org
обсуждение исходный текст
Список pgsql-committers
Log Message:
-----------
Adjust nodeBitmapIndexscan to keep the target index opened from plan
startup to end, rather than re-opening it in each MultiExecBitmapIndexScan
call.  I had foolishly thought that opening/closing wouldn't be much
more expensive than a rescan call, but that was sheer brain fade.

This seems to fix about half of the performance lossage reported by
Sergey Koposov.  I'm still not sure where the other half went.

Modified Files:
--------------
    pgsql/src/backend/executor:
        nodeBitmapIndexscan.c (r1.7 -> r1.8)

(http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/executor/nodeBitmapIndexscan.c.diff?r1=1.7&r2=1.8)
    pgsql/src/include/nodes:
        execnodes.h (r1.130 -> r1.131)
        (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/include/nodes/execnodes.h.diff?r1=1.130&r2=1.131)

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

Предыдущее
От: momjian@svr1.postgresql.org (Bruce Momjian)
Дата:
Сообщение: pgsql: Update "control" item.
Следующее
От: neilc@svr1.postgresql.org (Neil Conway)
Дата:
Сообщение: pgsql: The issue has been raised in the past that our build system links