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 <[email protected]> Author: Ayush Tiwari <[email protected]> Reviewed-by: Fujii Masao <[email protected]> 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 Branch ------ master Details ------- https://git.postgresql.org/pg/commitdiff/9f07de2053163cda9acb68c34d8be4b56f9659d4 Modified Files -------------- src/test/recovery/t/031_recovery_conflict.pl | 3 +++ 1 file changed, 3 insertions(+)
