Alvaro Herrera <alvherre@alvh.no-ip.org> writes:
> Fix WAL replay of locking an updated tuple
The test added by this patch certainly looks like it's backwards.
Shouldn't you be clearing HOT_UPDATED only if the tuple is *not*
XMAX_IS_LOCKED_ONLY?
If the code is actually correct as written, then I think that test
macro is very unfortunately named.
regards, tom lane
