"Anton A. Melnikov" <a.melnikov@postgrespro.ru> writes:
> Seems it is possible to exclude much less code from checking
> under valgrind and get the same result by replacing the only
> function call pg_rightmost_one_pos64() with a valgrind-safe
> code. See the attached patch, please.
There is no place anywhere in our code base where we hide unsafe
code from valgrind rather than fixing said code. This does not
seem like a place to start such an ugly practice. Performance
does not trump everything else.
I'd be inclined to just remove the pg_rightmost_one_pos64 call
in favor of the other coding you suggest.
regards, tom lane