Re: WSL (windows subsystem on linux) users will need to turn fsync off as of 11.2 - Mailing list pgsql-general

From Tom Lane
Subject Re: WSL (windows subsystem on linux) users will need to turn fsync off as of 11.2
Date
Msg-id 6944.1550204939@sss.pgh.pa.us
Whole thread Raw
In response to Re: WSL (windows subsystem on linux) users will need to turn fsyncoff as of 11.2  (Thomas Munro <thomas.munro@enterprisedb.com>)
Responses Re: WSL (windows subsystem on linux) users will need to turn fsyncoff as of 11.2  (Thomas Munro <thomas.munro@enterprisedb.com>)
List pgsql-general
Thomas Munro <thomas.munro@enterprisedb.com> writes:
>> On Fri, Feb 15, 2019 at 2:56 PM Bruce Klein <brucek@gmail.com> wrote:
>>> In 11.1 did you see the message "WARNING: could not flush dirty data: Function not implemented"
>> Yes

> Here is a place where people go to complain about that:
> https://github.com/Microsoft/WSL/issues/645
> I suppose we could tolerate ENOSYS.

What I'm not grasping here is why you considered that sync_file_range
failure should be treated as a reason to PANIC in the first place?
Surely it is not fsync(), nor some facsimile thereof.  In fact, if
any of the branches in pg_flush_data really need the data_sync_elevel
treatment, somebody's mental model of that operation needs adjustment.
Maybe it's mine.

            regards, tom lane


pgsql-general by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: Shared hosting with FDW on AWS RDS
Next
From: Thomas Munro
Date:
Subject: Re: WSL (windows subsystem on linux) users will need to turn fsyncoff as of 11.2