Alvaro Herrera <[email protected]> writes:
> ! if (!(tuple->t_infomask & HEAP_XMAX_INVALID))
> {
> ! if (!(tuple->t_infomask & HEAP_XMAX_IS_MULTI))
How about just one test,
if (!(tuple->t_infomask & (HEAP_XMAX_INVALID | HEAP_XMAX_IS_MULTI)))
But other than that quibble, yeah, it's a bug. XMAX_INVALID means just
that: the xmax is not to be thought valid.
regards, tom lane
--
Sent via pgsql-hackers mailing list ([email protected])
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
