amcheck: In verify_heapam, allows tuples with xmin 0. Commit e88754a1965c0f40a723e6e46d670cacda9e19bd caused that case to be reported as corruption, but Peter Geoghegan pointed out that it can legitimately happen in the case of a speculative insertion that aborts, so we'd better not flag it as corruption after all.
Back-patch to v14, like the commit that introduced the issue. Discussion: http://postgr.es/m/cah2-wzmeabzcptxsy-nxkh6qt3fkapyhgqse2ptvggj17zq...@mail.gmail.com Branch ------ REL_14_STABLE Details ------- https://git.postgresql.org/pg/commitdiff/e3363cda9cb615718be14e2780fa4c82f3d270de Modified Files -------------- contrib/amcheck/verify_heapam.c | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-)
