Postgres Pro
Downloads
Home   >   mailing lists

pgsql: Adjust nodeBitmapIndexscan to keep the target index opened from - Mailing list pgsql-committers

From tgl@svr1.postgresql.org (Tom Lane)
Subject pgsql: Adjust nodeBitmapIndexscan to keep the target index opened from
Date
Msg-id 20050505033723.C216B52A37@svr1.postgresql.org
Whole thread Raw
List pgsql-committers
Tree view 
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 by date:

Previous
From: momjian@svr1.postgresql.org (Bruce Momjian)
Date:
Subject: pgsql: Update "control" item.
Next
From: neilc@svr1.postgresql.org (Neil Conway)
Date:
Subject: pgsql: The issue has been raised in the past that our build system links