Re: Changing default value of wal_sync_method to open_datasync on Linux - Mailing list pgsql-hackers

From Robert Haas
Subject Re: Changing default value of wal_sync_method to open_datasync on Linux
Date
Msg-id CA+TgmoY6LG1Ptr2N2K1a5nMu1VMCKEi5DvV0XZKFXmJfnJmLFw@mail.gmail.com
Whole thread Raw
In response to Changing default value of wal_sync_method to open_datasync on Linux  ("Tsunakawa, Takayuki" <tsunakawa.takay@jp.fujitsu.com>)
Responses Re: Changing default value of wal_sync_method to open_datasync on Linux  ("MauMau" <maumau307@gmail.com>)
List pgsql-hackers
On Mon, Feb 19, 2018 at 7:27 PM, Tsunakawa, Takayuki
<tsunakawa.takay@jp.fujitsu.com> wrote:
> The reason for change is better performance.  Robert Haas said open_datasync was much faster than fdatasync with
NVRAMin this thread:
 

I also said it would be worse on spinning disks.

Also, Yoshimi Ichiyanagi did not find it to be true even on NVRAM.

Changing the default requires a lot more than one test result where a
non-default setting is better.

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: [HACKERS] VACUUM and ANALYZE disagreeing on what reltuples means
Next
From: Robert Haas
Date:
Subject: Re: Typo with pg_multixact/offset in multixact.c