mirror of
https://git.postgresql.org/git/postgresql.git
synced 2025-03-31 20:20:44 +08:00
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-NXKH6Qt3FkAPYHGQSe2PtvGgj17ZQkCw@mail.gmail.com
This commit is contained in:
parent
bade01cb4d
commit
b7cea58822
@ -1032,8 +1032,7 @@ check_tuple_visibility(HeapCheckContext *ctx, bool *xmin_commit_status_ok,
|
||||
switch (get_xid_status(xmin, ctx, &xmin_status))
|
||||
{
|
||||
case XID_INVALID:
|
||||
report_corruption(ctx,
|
||||
pstrdup("xmin is invalid"));
|
||||
/* Could be the result of a speculative insertion that aborted. */
|
||||
return false;
|
||||
case XID_BOUNDS_OK:
|
||||
*xmin_commit_status_ok = true;
|
||||
|
Loading…
x
Reference in New Issue
Block a user