pgsql: Revert my best_inner_indexscan patch of yesterday, which turns - Mailing list pgsql-committers

From tgl@postgresql.org (Tom Lane)
Subject pgsql: Revert my best_inner_indexscan patch of yesterday, which turns
Date
Msg-id 20060409181844.9EFDF11F74F0@postgresql.org
Whole thread Raw
List pgsql-committers
Log Message:
-----------
Revert my best_inner_indexscan patch of yesterday, which turns out to have
had a bad side-effect: it stopped finding plans that involved BitmapAnd
combinations of indexscans using both join and non-join conditions.  Instead,
make choose_bitmap_and more aggressive about detecting redundancies between
BitmapOr subplans.

Modified Files:
--------------
    pgsql/src/backend/optimizer/path:
        indxpath.c (r1.203 -> r1.204)
        (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/optimizer/path/indxpath.c.diff?r1=1.203&r2=1.204)

pgsql-committers by date:

Previous
From: andrewd@pgfoundry.org (User Andrewd)
Date:
Subject: pgbuildfarm - client-code: Do CVS status check in chunks to avoid
Next
From: tgl@postgresql.org (Tom Lane)
Date:
Subject: pgsql: Revert my best_inner_indexscan patch of yesterday, which turns