Thread: pgsql: Fix best_inner_indexscan to actually enforce that an "inner

pgsql: Fix best_inner_indexscan to actually enforce that an "inner

From

tgl@postgresql.org (Tom Lane)

Date:

08 April 2006, 18:32:21

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)