aboutsummaryrefslogtreecommitdiff
path: root/src/backend/commands/dbcommands.c
diff options
context:
space:
mode:
authorTom Lane <tgl@sss.pgh.pa.us>2005-03-02 04:10:53 +0000
committerTom Lane <tgl@sss.pgh.pa.us>2005-03-02 04:10:53 +0000
commit3104a928663d5dc3ff159cb59636845131f1da08 (patch)
tree79c2cc38fa79b98540873276e8e2acdf46709f19 /src/backend/commands/dbcommands.c
parent47ea7148e3c11deee92e6eda336ca483bd6a858c (diff)
downloadpostgresql-3104a928663d5dc3ff159cb59636845131f1da08.tar.gz
postgresql-3104a928663d5dc3ff159cb59636845131f1da08.zip
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.
Diffstat (limited to 'src/backend/commands/dbcommands.c')
0 files changed, 0 insertions, 0 deletions