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

Commit0ddaaa4

Browse files
committed
Relax overly strict sanity check for upgraded ancient databases
Commit4800f16 added some sanity checks to ensure we don'taccidentally corrupt data, but in one of them we failed to consider theeffects of a database upgraded from 9.2 or earlier, where a tupleexclusively locked prior to the upgrade has a slightly different bitpattern. Fix that by using the macro that we fixed in commit74ebba8 for similar situations.Reported-by: Alexandre GarciaReviewed-by: Andres FreundDiscussion:https://postgr.es/m/CAPYLKR6yxV4=pfW0Gwij7aPNiiPx+3ib4USVYnbuQdUtmkMaEA@mail.gmail.comAndres suspects that this bug may have wider ranging consequences, but Icouldn't find anything.
1 parent3f26be8 commit0ddaaa4

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

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

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -6783,7 +6783,7 @@ heap_prepare_freeze_tuple(HeapTupleHeader tuple,
67836783
* independent of committedness, since a committed lock holder has
67846784
* released the lock).
67856785
*/
6786-
if (!(tuple->t_infomask&HEAP_XMAX_LOCK_ONLY)&&
6786+
if (!HEAP_XMAX_IS_LOCKED_ONLY(tuple->t_infomask)&&
67876787
TransactionIdDidCommit(xid))
67886788
ereport(ERROR,
67896789
(errcode(ERRCODE_DATA_CORRUPTED),

0 commit comments

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