Skip site navigation (1) Skip section navigation (2)

pgsql: While determining the filter clauses for an index scan (either

From: tgl(at)svr1(dot)postgresql(dot)org (Tom Lane)
To: pgsql-committers(at)postgresql(dot)org
Subject: pgsql: While determining the filter clauses for an index scan (either
Date: 2005-04-25 03:58:30
Message-ID: 20050425035830.D295A5349D@svr1.postgresql.org (view raw or flat)
Thread:
Lists: 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

Next:From: Tom LaneDate: 2005-04-25 04:27:13
Subject: pgsql: Avoid rechecking lossy operators twice in a bitmap scan plan.
Previous:From: Tom LaneDate: 2005-04-25 02:14:48
Subject: pgsql: Replace slightly klugy create_bitmap_restriction() function with

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group