Hi Antonin,
Thanks for your update.
I think v04 fixes the finalize_block_range() problem.
The compute_new_xmax_infomask() Assert is easy to hit. The
AccessExclusiveLock in rebuild_relation_finish_concurrent() assigns an
XID, so any UPDATE or DELETE committed while REPACK waits for it fails
on replay. The attached spec does it every time.
If you give the new counter a slot that index builds don't write,
like 13, 0008 does not have to depend on 6958.
Thanks,
Shihao
