| From: | Thomas Munro <thomas(dot)munro(at)enterprisedb(dot)com> |
|---|---|
| To: | Bruce Klein <brucek(at)gmail(dot)com> |
| Cc: | Ravi Krishna <srkrishna100(at)aol(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "pgsql-generallists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: WSL (windows subsystem on linux) users will need to turn fsync off as of 11.2 |
| Date: | 2019-02-15 03:14:13 |
| Message-ID: | CAEepm=0z5Ev43XS6NcdEqw09sC7fCLa1dYUhaVPs30K0wPh-xA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Fri, Feb 15, 2019 at 3:56 PM Thomas Munro
<thomas(dot)munro(at)enterprisedb(dot)com> wrote:
> On Fri, Feb 15, 2019 at 2:56 PM Bruce Klein <brucek(at)gmail(dot)com> wrote:
> > > In 11.1 did you see the message "WARNING: could not flush dirty data: Function not implemented"
> > Yes
>
> I wonder if this is coming from sync_file_range(), which is not
> implemented on WSL according to random intergoogling, but probably
> appears as present to our configure script. I find it harder to
> believe they didn't implement fsync().
Here is a place where people go to complain about that:
https://github.com/Microsoft/WSL/issues/645
I suppose we could tolerate ENOSYS.
--
Thomas Munro
http://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2019-02-15 03:21:15 | Re: Shared hosting with FDW on AWS RDS |
| Previous Message | Thomas Munro | 2019-02-15 02:56:54 | Re: WSL (windows subsystem on linux) users will need to turn fsync off as of 11.2 |