Gregory Stark <stark@enterprisedb.com> writes:
> Fwiw, these two call sites are only for when HeapTupleSatisfiesMVCC finds a
> tuples which has been moved away by VACUUM FULL... The latter for when it
> finds such a tuple but the VACUUM FULL aborted.
> It seems quite likely that the compiler is actually right (by chance) and we
> shouldn't be optimizing those cases at the expense of more common cases.
I trimmed the original message quite a bit --- there were a lot more
than two call sites that it was deciding not to inline. Maybe it's
making the right choices or maybe not.
regards, tom lane