From c642a764af508d578f37008e24bd9d32738ac734 Mon Sep 17 00:00:00 2001 From: Man Zeng Date: Wed, 21 Jan 2026 22:16:32 +0800 Subject: [PATCH 1/2] fix: hardcode offset 43 in expected tuple error regex Align expected error message with comment logic - the corrupted successor tuple should be at offset 43, not arbitrary offset. Update regex to match offset 43 instead of \d+ for accurate error validation. --- src/bin/pg_amcheck/t/004_verify_heapam.pl | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/bin/pg_amcheck/t/004_verify_heapam.pl b/src/bin/pg_amcheck/t/004_verify_heapam.pl index 95f1f34c90d..f9c76f4b460 100644 --- a/src/bin/pg_amcheck/t/004_verify_heapam.pl +++ b/src/bin/pg_amcheck/t/004_verify_heapam.pl @@ -720,7 +720,7 @@ for (my $tupidx = 0; $tupidx < $ROWCOUNT; $tupidx++) $tup->{t_xmax} = $in_progress_xid; $tup->{t_infomask} &= ~HEAP_XMIN_COMMITTED; push @expected, - qr/${header}tuple with aborted xmin \d+ was updated to produce a tuple at offset \d+ with in-progress xmin \d+/; + qr/${header}tuple with aborted xmin \d+ was updated to produce a tuple at offset 43 with in-progress xmin \d+/; } elsif ($offnum == 40) { -- 2.45.2