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

Commitf6661d3

Browse files
committed
Fix use of wrong index in ComputeXidHorizons().
This bug, recently introduced in941697c, at least lead to vacuumfailing because it found tuples inserted by a running transaction, butbelow the freeze limit. The freeze limit in turn is directly affectedby the aforementioned bug.Thanks to Tom Lane figuring how to make the bug reproducible.We should add a few more assertions to make sure this type of bugisn't as hard to notice, but it's not yet clear how to best do so.Co-Diagnosed-By: Tom Lane <tgl@sss.pgh.pa.us>Author: Andres Freund <andres@anarazel.de>Discussion:https://postgr.es/m/1013484.1597609043@sss.pgh.pa.us
1 parent49967da commitf6661d3

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

‎src/backend/storage/ipc/procarray.c

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1663,7 +1663,7 @@ ComputeXidHorizons(ComputeXidHorizonsResult *h)
16631663
TransactionIdxmin;
16641664

16651665
/* Fetch xid just once - see GetNewTransactionId */
1666-
xid=UINT32_ACCESS_ONCE(other_xids[pgprocno]);
1666+
xid=UINT32_ACCESS_ONCE(other_xids[index]);
16671667
xmin=UINT32_ACCESS_ONCE(proc->xmin);
16681668

16691669
/*

0 commit comments

Comments
 (0)

[8]ページ先頭

©2009-2025 Movatter.jp