pgsql: Fix best_inner_indexscan to actually enforce that an "inner

Поиск
Список
Период
Сортировка
От tgl@postgresql.org (Tom Lane)
Тема pgsql: Fix best_inner_indexscan to actually enforce that an "inner
Дата
Msg-id 20060408213226.1F32511F6AEE@postgresql.org
обсуждение исходный текст
Список pgsql-committers
Log Message:
-----------
Fix best_inner_indexscan to actually enforce that an "inner indexscan" use
at least one join condition as an indexqual.  Before bitmap indexscans, this
oversight didn't really cost much except for redundantly considering the
same join paths twice; but as of 8.1 it could result in silly bitmap scans
that would do the same BitmapOr twice and then BitmapAnd these together :-(

Tags:
----
REL8_1_STABLE

Modified Files:
--------------
    pgsql/src/backend/optimizer/path:
        indxpath.c (r1.191.2.5 -> r1.191.2.6)

(http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/optimizer/path/indxpath.c.diff?r1=1.191.2.5&r2=1.191.2.6)

В списке pgsql-committers по дате отправления:

Предыдущее
От: tgl@postgresql.org (Tom Lane)
Дата:
Сообщение: pgsql: Fix best_inner_indexscan to actually enforce that an "inner
Следующее
От: fxjr@pgfoundry.org (User Fxjr)
Дата:
Сообщение: npgsql - Npgsql: 2006-04-08 Francisco Figueiredo Jr.