From b6ee30ec0866619eafc10cf43c4714ed1b89fec6 Mon Sep 17 00:00:00 2001 From: Robert Haas Date: Wed, 31 Jan 2024 11:35:41 -0500 Subject: [PATCH] In 002_blocks.pl, try to prevent a HOT update. Make the new tuple larger than the old one so that it, hopefully, won't manage to squeeze into leftover freespace on the same page. The test is trying to verify that the UPDATE touches 2 pages, but if a HOT update happens, then it doesn't. Per buildfarm. --- src/bin/pg_walsummary/t/002_blocks.pl | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/src/bin/pg_walsummary/t/002_blocks.pl b/src/bin/pg_walsummary/t/002_blocks.pl index 723285943f5..c1303b188cf 100644 --- a/src/bin/pg_walsummary/t/002_blocks.pl +++ b/src/bin/pg_walsummary/t/002_blocks.pl @@ -56,7 +56,8 @@ note_wal_summary_dir("after insert", $node1); # Update a row in the first block of the table and trigger a checkpoint. $node1->safe_psql('postgres', <