Heikki Linnakangas <heikki@enterprisedb.com> writes:
> AFAICS, we can just simply remove the assertion. But is there any
> codepaths that assume that after calling HeapTupleSatisfiesSnapshot, all
> appropriate hint bits are set?
There had better not be, since we are going to postpone setting hint
bits for recently-committed transactions as part of the async-commit
patch.
A quick grep suggests that VACUUM FULL might be at risk here.
regards, tom lane