pgsql: Rearrange code in ExecInitBitmapHeapScan so that we don't

Поиск
Список
Период
Сортировка
От tgl@postgresql.org (Tom Lane)
Тема pgsql: Rearrange code in ExecInitBitmapHeapScan so that we don't
Дата
Msg-id 20051202013027.4C31A9DD6E5@postgresql.org
обсуждение исходный текст
Список pgsql-committers
Дерево обсуждения 
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 по дате отправления:

Предыдущее
От: tgl@postgresql.org (Tom Lane)
Дата:
Сообщение: pgsql: Rearrange code in ExecInitBitmapHeapScan so that we don't
Следующее
От: chriskl@pgfoundry.org (User Chriskl)
Дата:
Сообщение: mysqlcompat - mysqlcompat: Add benchmark(), coercibility(), bit_count()