From: | tgl(at)svr1(dot)postgresql(dot)org (Tom Lane) |
---|---|
To: | pgsql-committers(at)postgresql(dot)org |
Subject: | pgsql: Another go at making pred_test() handle all reasonable |
Date: | 2005-03-02 04:10:54 |
Message-ID: | 20050302041054.C523B55BBB@svr1.postgresql.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | 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)
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2005-03-02 05:22:23 | pgsql: Prevent large allocation in snprintf to hold positional |
Previous Message | Bruce Momjian | 2005-03-02 03:21:52 | pgsql: Fix snprintf on Win32: * If vsnprintf() is not before |