pgsql: Adjust nodeBitmapIndexscan to keep the target index opened from

From: tgl(at)svr1(dot)postgresql(dot)org (Tom Lane)
To: pgsql-committers(at)postgresql(dot)org
Subject: pgsql: Adjust nodeBitmapIndexscan to keep the target index opened from
Date: 2005-05-05 03:37:23
Message-ID: 20050505033723.C216B52A37@svr1.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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)

Browse pgsql-committers by date

  From Date Subject
Next Message Neil Conway 2005-05-05 11:50:18 pgsql: The issue has been raised in the past that our build system links
Previous Message Bruce Momjian 2005-05-05 01:42:04 pgsql: Update "control" item.