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

Commitd1e9079

Browse files
committed
Ignore nextOid when replaying an ONLINE checkpoint.
The nextOid value is from the start of the checkpoint and may well be stalecompared to values from more recent XLOG_NEXTOID records. Previously, weadopted it anyway, allowing the OID counter to go backwards during a crash.While this should be harmless, it contributed to the severity of the bugfixed in commit0408e1e, by allowing duplicate TOAST OIDs to be assignedimmediately following a crash. Without this error, that issue would onlyhave arisen when TOAST objects just younger than a multiple of 2^32 OIDswere deleted and then not vacuumed in time to avoid a conflict.Pavan DeolaseeDiscussion:https://postgr.es/m/CABOikdOgWT2hHkYG3Wwo2cyZJq2zfs1FH0FgX-=h4OLosXHf9w@mail.gmail.com
1 parent0408e1e commitd1e9079

File tree

1 file changed

+14
-5
lines changed
  • src/backend/access/transam

1 file changed

+14
-5
lines changed

‎src/backend/access/transam/xlog.c

Lines changed: 14 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -9785,11 +9785,20 @@ xlog_redo(XLogReaderState *record)
97859785
checkPoint.nextXid))
97869786
ShmemVariableCache->nextXid=checkPoint.nextXid;
97879787
LWLockRelease(XidGenLock);
9788-
/* ... but still treat OID counter as exact */
9789-
LWLockAcquire(OidGenLock,LW_EXCLUSIVE);
9790-
ShmemVariableCache->nextOid=checkPoint.nextOid;
9791-
ShmemVariableCache->oidCount=0;
9792-
LWLockRelease(OidGenLock);
9788+
9789+
/*
9790+
* We ignore the nextOid counter in an ONLINE checkpoint, preferring
9791+
* to track OID assignment through XLOG_NEXTOID records. The nextOid
9792+
* counter is from the start of the checkpoint and might well be stale
9793+
* compared to later XLOG_NEXTOID records. We could try to take the
9794+
* maximum of the nextOid counter and our latest value, but since
9795+
* there's no particular guarantee about the speed with which the OID
9796+
* counter wraps around, that's a risky thing to do. In any case,
9797+
* users of the nextOid counter are required to avoid assignment of
9798+
* duplicates, so that a somewhat out-of-date value should be safe.
9799+
*/
9800+
9801+
/* Handle multixact */
97939802
MultiXactAdvanceNextMXact(checkPoint.nextMulti,
97949803
checkPoint.nextMultiOffset);
97959804

0 commit comments

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