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. Branch ------ master Details ------- https://git.postgresql.org/pg/commitdiff/b6ee30ec0866619eafc10cf43c4714ed1b89fec6 Modified Files -------------- src/bin/pg_walsummary/t/002_blocks.pl | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-)