aboutsummaryrefslogtreecommitdiff
path: root/contrib/btree_gist/btree_bit.c
diff options
context:
space:
mode:
authorTom Lane <tgl@sss.pgh.pa.us>2005-03-01 00:24:52 +0000
committerTom Lane <tgl@sss.pgh.pa.us>2005-03-01 00:24:52 +0000
commit4e89bae704f79af8b2b6ac3d43ea963c22df1947 (patch)
tree21435cacd63b09cca62dbb710fd041081f534c06 /contrib/btree_gist/btree_bit.c
parent5c4a91c2958638ce9ec5f08c28dcddb88f4c0bd9 (diff)
downloadpostgresql-4e89bae704f79af8b2b6ac3d43ea963c22df1947.tar.gz
postgresql-4e89bae704f79af8b2b6ac3d43ea963c22df1947.zip
Revert the logic for expanding AND/OR conditions in pred_test() to what
it was in 7.4, and add some comments explaining why it has to be this way. I broke it for OR'd index predicates in a fit of code cleanup last summer. Per example from Sergey Koshcheyev.
Diffstat (limited to 'contrib/btree_gist/btree_bit.c')
0 files changed, 0 insertions, 0 deletions