Re: pgsql: Avoid resetting Xmax when it's a multi with an aborted update

Alvaro Herrera <alvherre@alvh.no-ip.org> writes:
> Avoid resetting Xmax when it's a multi with an aborted update

I may be confused, but this patch doesn't look like it does what
your commit log message says.  It looks to me like the logic for
setting the hint bit is exactly the same as before; what's changed
is only the return code from HeapTupleSatisfiesUpdate.

The code looks right, though.  Is it just that your commit message
misdescribes it?

            regards, tom lane