Re: Recommended value for pg_test_fsync - Mailing list pgsql-performance

From Bruce Momjian
Subject Re: Recommended value for pg_test_fsync
Date
Msg-id 20200630152408.GA28711@momjian.us
Whole thread Raw
In response to Re: Recommended value for pg_test_fsync  (Nikhil Shetty <nikhil.dba04@gmail.com>)
Responses Re: Recommended value for pg_test_fsync  (Nikhil Shetty <nikhil.dba04@gmail.com>)
List pgsql-performance
On Tue, Jun 30, 2020 at 10:32:13AM +0530, Nikhil Shetty wrote:
> Hi Bruce,
> 
> Based on pg_test_fsync results, should we choose open_datasync or fdatasync as
> wal_sync_method? Can we rely on pg_test_fsync for choosing the best

I would just pick the fastest method, but if the method is _too_ fast,
it might mean that it isn't actually writing to durable storage.

> wal_sync_method or is there any other way?

pg_test_fsync is the only way I know of, which is why I wrote it.

-- 
  Bruce Momjian  <bruce@momjian.us>        https://momjian.us
  EnterpriseDB                             https://enterprisedb.com

  The usefulness of a cup is in its emptiness, Bruce Lee




pgsql-performance by date:

Previous
From: Nikhil Shetty
Date:
Subject: Re: Recommended value for pg_test_fsync
Next
From: Gunther Schadow
Date:
Subject: Is there a known bug with SKIP LOCKED and "tuple to be locked was already moved to another partition due to concurrent update"?