- Fix incorrect result of rb_and (#22)
This is a very serious bug, and the calculation results of some functions are wrong. Below is a simple example.
postgres=# SELECT '{100373,1829130,1861002,1975442,2353213,2456403}'::roaringbitmap & '{2353213}'::roaringbitmap;
?column?
----------
{}
(1 row)
Functions with the same problem include rb_or_cardinality,rb_and,rb_and_cardinality,rb_andnot,rb_andnot_cardinality,rb_xor_cardinality,rb_intersect,rb_contains,rb_containedby,rb_jaccard_dist,rb_index.
The affected versions are 0.5.2 and 0.5.3, users should upgrade as soon as possible.