Postgres Pro
Downloads
Home   >   mailing lists

pgsql: Rearrange code in ExecInitBitmapHeapScan so that we don't - Mailing list pgsql-committers

From tgl@postgresql.org (Tom Lane)
Subject pgsql: Rearrange code in ExecInitBitmapHeapScan so that we don't
Date
Msg-id 20051202013027.4C31A9DD6E5@postgresql.org
Whole thread Raw
List pgsql-committers
Tree view 
Log Message:
-----------
Rearrange code in ExecInitBitmapHeapScan so that we don't initialize the
child plan nodes until we have acquired lock on the relation to scan.
The relative order of initialization of plan nodes isn't real important in
other cases, but it's critical here because one is supposed to lock a
relation before its indexes, not vice versa.  The original coding was at
least vulnerable to deadlock against DROP INDEX, and perhaps worse things.

Tags:
----
REL8_1_STABLE

Modified Files:
--------------
    pgsql/src/backend/executor:
        nodeBitmapHeapscan.c (r1.4 -> r1.4.2.1)

(http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/executor/nodeBitmapHeapscan.c.diff?r1=1.4&r2=1.4.2.1)

pgsql-committers by date:

Previous
From: tgl@postgresql.org (Tom Lane)
Date:
Subject: pgsql: Rearrange code in ExecInitBitmapHeapScan so that we don't
Next
From: chriskl@pgfoundry.org (User Chriskl)
Date:
Subject: mysqlcompat - mysqlcompat: Add benchmark(), coercibility(), bit_count()