From a7f4171071bbcdec79e8afa4cad1bc6951b098cc Mon Sep 17 00:00:00 2001
From: Tom Lane <tgl@sss.pgh.pa.us>
Date: Wed, 19 Jan 2022 12:36:49 -0500
Subject: [PATCH] Don't enable fsync in
src/test/recovery/t/008_fsm_truncation.pl.
In adverse circumstances, the fsync calls cause this test to run for
quite a long time (multiple minutes) and even suffer timeout failures.
This seems to date from before we made an effort to disable fsync in
all our test cases; there's not a lot of point in using it if there's
not a plan to force an O/S crash during the test.
Discussion: https://postgr.es/m/440239.1642560607@sss.pgh.pa.us
---
src/test/recovery/t/008_fsm_truncation.pl | 1 -
1 file changed, 1 deletion(-)
diff --git a/src/test/recovery/t/008_fsm_truncation.pl b/src/test/recovery/t/008_fsm_truncation.pl
index cbf6e217d9..ee48c217cf 100644
--- a/src/test/recovery/t/008_fsm_truncation.pl
+++ b/src/test/recovery/t/008_fsm_truncation.pl
@@ -17,7 +17,6 @@ $node_primary->init(allows_streaming => 1);
$node_primary->append_conf(
'postgresql.conf', qq{
-fsync = on
wal_log_hints = on
max_prepared_transactions = 5
autovacuum = off