Re: "unaddressable bytes" in BRIN

* Alvaro Herrera (alvherre(at)2ndquadrant(dot)com) wrote:
> What I think this means is that during an index build
> brin_minmax_add_value() called numeric_lt() which detoasted one of its
> input values; later, brin_doinsert() inserts a tuple containing the
> value, but it tries to use more bytes than were allocated. I haven't
> had time to actually study what is going on here, but wanted to archive
> this publicly. (Value detoasting evidently plays a role here, but I
> don't know how.)

I went ahead and added this to the 9.5 open items list.

Thanks!

Stephen