pgsql: Adjust nodeBitmapIndexscan.c to not keep the index open across

From: tgl(at)svr1(dot)postgresql(dot)org (Tom Lane)
To: pgsql-committers(at)postgresql(dot)org
Subject: pgsql: Adjust nodeBitmapIndexscan.c to not keep the index open across
Date: 2005-04-24 18:16:38
Message-ID: 20050424181638.9AF0354310@svr1.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

Log Message:
-----------
Adjust nodeBitmapIndexscan.c to not keep the index open across calls,
but just to open and close it during MultiExecBitmapIndexScan. This
avoids acquiring duplicate resources (eg, multiple locks on the same
relation) in a tree with many bitmap scans. Also, don't bother to
lock the parent heap at all here, since we must be underneath a
BitmapHeapScan node that will be holding a suitable lock.

Modified Files:
--------------
pgsql/src/backend/executor:
nodeBitmapIndexscan.c (r1.5 -> r1.6)
(http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/executor/nodeBitmapIndexscan.c.diff?r1=1.5&r2=1.6)
pgsql/src/include/nodes:
execnodes.h (r1.127 -> r1.128)
(http://developer.postgresql.org/cvsweb.cgi/pgsql/src/include/nodes/execnodes.h.diff?r1=1.127&r2=1.128)

Browse pgsql-committers by date

  From Date Subject
Next Message Joshua D. Drake 2005-04-24 18:40:50 Re: [COMMITTERS] pgsql: Remove replicaiton FAQ item.
Previous Message Jeff Davis 2005-04-24 18:04:42 Re: [COMMITTERS] pgsql: Remove replicaiton FAQ item.