From: Tom Lane <tgl@sss.pgh.pa.us>
To: pgsql-committers@lists.postgresql.org
Subject: pgsql: Don't enable fsync in src/test/recovery/t/008_fsm_truncation.pl.
Date: Wed, 19 Jan 2022 17:37:04 +0000
Message-ID: <E1nAEtM-00059m-D5@gemulon.postgresql.org> (raw)
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
Branch
------
master
Details
-------
https://git.postgresql.org/pg/commitdiff/a7f4171071bbcdec79e8afa4cad1bc6951b098cc
Modified Files
--------------
src/test/recovery/t/008_fsm_truncation.pl | 1 -
1 file changed, 1 deletion(-)
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-committers@postgresql.org
Cc: tgl@sss.pgh.pa.us
Subject: Re: pgsql: Don't enable fsync in src/test/recovery/t/008_fsm_truncation.pl.
In-Reply-To: <E1nAEtM-00059m-D5@gemulon.postgresql.org>
References: <E1nAEtM-00059m-D5@gemulon.postgresql.org>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox