diff options
| author | Tom Lane | 2022-01-19 17:36:49 +0000 |
|---|---|---|
| committer | Tom Lane | 2022-01-19 17:36:49 +0000 |
| commit | a7f4171071bbcdec79e8afa4cad1bc6951b098cc (patch) | |
| tree | df866427b250c6d5892711af8aa3f1de32601988 /src/test | |
| parent | 89f059bdf52cc9a86b890d42ceed92237123479e (diff) | |
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
Diffstat (limited to 'src/test')
| -rw-r--r-- | src/test/recovery/t/008_fsm_truncation.pl | 1 |
1 files changed, 0 insertions, 1 deletions
diff --git a/src/test/recovery/t/008_fsm_truncation.pl b/src/test/recovery/t/008_fsm_truncation.pl index cbf6e217d95..ee48c217cfe 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 |