pgsql: Another go at making pred_test() handle all reasonable - Mailing list pgsql-committers

From tgl@svr1.postgresql.org (Tom Lane)
Subject pgsql: Another go at making pred_test() handle all reasonable
Date
Msg-id 20050302041054.C523B55BBB@svr1.postgresql.org
Whole thread Raw
List pgsql-committers
Log Message:
-----------
Another go at making pred_test() handle all reasonable combinations
of AND and OR clauses.  The key point here is that an OR on the
predicate side has to be treated gingerly: we may be able to prove
that the OR is implied even when no one of its components is implied.
For example (x OR y) implies (x OR y OR z) even though no one of x,
y, or z can be individually proven.  This code handles both the
example shown recently by Sergey Koshcheyev and the one shown last
October by Dawid Kuroczko.

Modified Files:
--------------
    pgsql/src/backend/optimizer/path:
        indxpath.c (r1.168 -> r1.169)
        (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/optimizer/path/indxpath.c.diff?r1=1.168&r2=1.169)

pgsql-committers by date:

Previous
From: momjian@svr1.postgresql.org (Bruce Momjian)
Date:
Subject: pgsql: Fix snprintf on Win32: * If vsnprintf() is not before
Next
From: momjian@svr1.postgresql.org (Bruce Momjian)
Date:
Subject: pgsql: Prevent large allocation in snprintf to hold positional