From: | Jeff Janes <jeff(dot)janes(at)gmail(dot)com> |
---|---|
To: | Nikhil Shetty <nikhil(dot)dba04(at)gmail(dot)com> |
Cc: | Bruce Momjian <bruce(at)momjian(dot)us>, Pgsql Performance <pgsql-performance(at)lists(dot)postgresql(dot)org> |
Subject: | Re: Recommended value for pg_test_fsync |
Date: | 2020-06-30 17:26:56 |
Message-ID: | CAMkU=1weUE+AKHjo3vOPFg55JB5jZLdKdkqGQnxKEq8rWuKfww@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
On Tue, Jun 30, 2020 at 1:02 AM Nikhil Shetty <nikhil(dot)dba04(at)gmail(dot)com>
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 wal_sync_method or is there any other way?
>
Probably the default of fdatasync. The place where pg_test_fsync would
tell me not to use fdatasync is if it were so fast that it was not credible
that it was honestly syncing the data. I don't think pg_test_fsync does a
good job of exercising the realistic differences between fdatasync and
open_datasync. So unless it shows that one of them is lying about the
durability, it doesn't offer much help.
Cheers,
Jeff
From | Date | Subject | |
---|---|---|---|
Next Message | Nikhil Shetty | 2020-07-01 16:55:58 | Re: Recommended value for pg_test_fsync |
Previous Message | Jeff Janes | 2020-06-30 16:21:23 | Re: Recommended value for pg_test_fsync |