pgsql: While determining the filter clauses for an index scan (either - Mailing list pgsql-committers

From tgl@svr1.postgresql.org (Tom Lane)
Subject pgsql: While determining the filter clauses for an index scan (either
Date
Msg-id 20050425035830.D295A5349D@svr1.postgresql.org
Whole thread Raw
List pgsql-committers
Log Message:
-----------
While determining the filter clauses for an index scan (either plain
or bitmap), use pred_test to be a little smarter about cases where a
filter clause is logically unnecessary.  This may be overkill for the
plain indexscan case, but it's definitely useful for OR'd bitmap scans.

Modified Files:
--------------
    pgsql/src/backend/optimizer/path:
        indxpath.c (r1.178 -> r1.179)
        (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/optimizer/path/indxpath.c.diff?r1=1.178&r2=1.179)
    pgsql/src/backend/optimizer/plan:
        createplan.c (r1.186 -> r1.187)

(http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/optimizer/plan/createplan.c.diff?r1=1.186&r2=1.187)

pgsql-committers by date:

Previous
From: tgl@svr1.postgresql.org (Tom Lane)
Date:
Subject: pgsql: Replace slightly klugy create_bitmap_restriction() function with
Next
From: tgl@svr1.postgresql.org (Tom Lane)
Date:
Subject: pgsql: Avoid rechecking lossy operators twice in a bitmap scan plan.