From 628b70d3a3a936afa84dbdc344c02ae990797573 Mon Sep 17 00:00:00 2001 From: Fujii Masao Date: Mon, 5 Oct 2026 13:02:44 +0900 Subject: [PATCH] Disable autovacuum in 031_recovery_conflict.pl Buildfarm members adder and drongo failed to observe the expected relation lock wait in the startup deadlock test. In adder's failure, autovacuum pruned dead rows before the test's explicit VACUUM FREEZE, canceling the standby backend too early and releasing the relation lock wait before the test could observe it. Fix this by disabling autovacuum for the test node, leaving the explicit VACUUM commands in control of when pruning occurs. This also prevents auto-analyze workers on other relations from holding back xmin and interfering with the snapshot conflict test. Backpatch to v17, where this test is enabled. Reported-by: Alexander Lakhin Author: Ayush Tiwari Reviewed-by: Fujii Masao Discussion: https://postgr.es/m/421c0aee-84c8-4c07-b4b9-263095479755%40gmail.com Discussion: https://postgr.es/m/714729ea-f536-0faf-353b-cbd5c8f241ea%40gmail.com Backpatch-through: 17 --- src/test/recovery/t/031_recovery_conflict.pl | 3 +++ 1 file changed, 3 insertions(+) diff --git a/src/test/recovery/t/031_recovery_conflict.pl b/src/test/recovery/t/031_recovery_conflict.pl index 6bc209bba04..e9819a900f3 100644 --- a/src/test/recovery/t/031_recovery_conflict.pl +++ b/src/test/recovery/t/031_recovery_conflict.pl @@ -22,6 +22,9 @@ $node_primary->append_conf( allow_in_place_tablespaces = on log_temp_files = 0 +# The test must control when pruning WAL is generated. +autovacuum = off + # for deadlock test max_prepared_transactions = 10