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

Commit63c844a

Browse files
Remove overzealous MultiXact freeze assertion.
When VACUUM determines that an existing MultiXact should use a freezeplan that sets xmax to InvalidTransactionId, the original Multi may ormay not be before OldestMxact. Remove an incorrect assertion thatexpected it to always be from before OldestMxact.Oversight in commit 4ce3af.Author: Peter Geoghegan <pg@bowt.ie>Reported-By: Hayato Kuroda <kuroda.hayato@fujitsu.com>Discussion:https://postgr.es/m/TYAPR01MB5866B24104FD80B5D7E65C3EF5ED9@TYAPR01MB5866.jpnprd01.prod.outlook.com
1 parent9814ff5 commit63c844a

File tree

1 file changed

+0
-1
lines changed

1 file changed

+0
-1
lines changed

‎src/backend/access/heap/heapam.c‎

Lines changed: 0 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -6615,7 +6615,6 @@ heap_prepare_freeze_tuple(HeapTupleHeader tuple,
66156615
* it'll leave nothing in xmax (neither an Xid nor a MultiXactId).
66166616
*/
66176617
Assert(flags&FRM_INVALIDATE_XMAX);
6618-
Assert(MultiXactIdPrecedes(xid,cutoffs->OldestMxact));
66196618
Assert(!TransactionIdIsValid(newxmax));
66206619

66216620
/* Will set t_infomask/t_infomask2 flags in freeze plan below */

0 commit comments

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