pgsql: Fix best_inner_indexscan to actually enforce that an "inner

From: tgl(at)postgresql(dot)org (Tom Lane)
To: pgsql-committers(at)postgresql(dot)org
Subject: pgsql: Fix best_inner_indexscan to actually enforce that an "inner
Date: 2006-04-08 21:32:26
Message-ID: 20060408213226.1F32511F6AEE@postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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)

Browse pgsql-committers by date

  From Date Subject
Next Message User Fxjr 2006-04-08 22:08:30 npgsql - Npgsql: 2006-04-08 Francisco Figueiredo Jr.
Previous Message Tom Lane 2006-04-08 21:32:17 pgsql: Fix best_inner_indexscan to actually enforce that an "inner