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.

diff --git a/src/bin/pg_walsummary/t/002_blocks.pl b/src/bin/pg_walsummary/t/002_blocks.pl
index 723285943f5a3fd481b922df94b4bc367ca177e4..c1303b188cfcfe7ed20c634c81e41642c168e815 100644 (file)
--- 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', <<EOM);
-UPDATE mytable SET b = 'abcdefghijklmnopqrstuvwxyz' WHERE a = 2;
+UPDATE mytable SET b = 'abcdefghijklmnopqrstuvwxyz' || b || '01234567890'
+       WHERE a = 2;
 CHECKPOINT;
 EOM