From: Bruce Momjian <bruce@momjian.us>
To: Nikhil Shetty <nikhil.dba04@gmail.com>
Cc: pgsql-performance@lists.postgresql.org
Subject: Re: Recommended value for pg_test_fsync
Date: Tue, 30 Jun 2020 11:24:08 -0400
Message-ID: <20200630152408.GA28711@momjian.us> (raw)
In-Reply-To: <CAFpL5VyhW4sXAxjo1AudYS+hHNrJeNy5fgPinWL6MT_Q1mGSNw@mail.gmail.com>
References: <CAFpL5Vx8KQ4sdH5Bp=nq-uLwsr7N2rHiD+osMaMRzmRADqFVtA@mail.gmail.com>
<20200629160638.GB17530@momjian.us>
<CAFpL5VyhW4sXAxjo1AudYS+hHNrJeNy5fgPinWL6MT_Q1mGSNw@mail.gmail.com>
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
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 using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: bruce@momjian.us, nikhil.dba04@gmail.com, pgsql-performance@lists.postgresql.org
Subject: Re: Recommended value for pg_test_fsync
In-Reply-To: <20200630152408.GA28711@momjian.us>
* 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