Movatterモバイル変換

[0]ホーム
URL:

Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

 Sign up
Appearance settings

Commite3363cd

Browse files
committed
amcheck: In verify_heapam, allows tuples with xmin 0.
Commite88754a caused that caseto be reported as corruption, but Peter Geoghegan pointed out thatit can legitimately happen in the case of a speculative insertionthat 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
1 parentc6f1f4e commite3363cd

File tree

1 file changed

+1
-2
lines changed

1 file changed

+1
-2
lines changed

‎contrib/amcheck/verify_heapam.c

Lines changed: 1 addition & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -774,8 +774,7 @@ check_tuple_visibility(HeapCheckContext *ctx)
774774
switch (get_xid_status(xmin,ctx,&xmin_status))
775775
{
776776
caseXID_INVALID:
777-
report_corruption(ctx,
778-
pstrdup("xmin is invalid"));
777+
/* Could be the result of a speculative insertion that aborted. */
779778
return false;
780779
caseXID_BOUNDS_OK:
781780
break;

0 commit comments

Comments
 (0)
[8]ページ先頭
©2009-2025 Movatter.jp