pgsql: Fix best_inner_indexscan to actually enforce that an "inner - Mailing list pgsql-committers

From tgl@postgresql.org (Tom Lane)
Subject pgsql: Fix best_inner_indexscan to actually enforce that an "inner
Date
Msg-id 20060408213217.8AC9311F6630@postgresql.org
Whole thread Raw
List 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 :-(

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

pgsql-committers by date:

Previous
From: dpage@pgfoundry.org (User Dpage)
Date:
Subject: psqlodbc - psqlodbc: Remove iodbc headers that we no longer ship.
Next
From: tgl@postgresql.org (Tom Lane)
Date:
Subject: pgsql: Fix best_inner_indexscan to actually enforce that an "inner