On Thu, Nov 8, 2018 at 3:04 PM Thomas Munro <thomas.mu...@enterprisedb.com> wrote: > My reasoning for choosing bms_join() is that it cannot fail, assuming > the heap is not corrupted. It simply ORs the two bit-strings into > whichever is the longer input string, and frees the shorter input > string. (In an earlier version I used bms_union(), this function's > non-destructive sibling, but then realised that it could fail to > allocate() causing us to lose track of a 1 bit).
Oh, OK. I was assuming it was allocating. -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company
