| From: | James Sewell <james(dot)sewell(at)jirotech(dot)com> |
|---|---|
| To: | Andres Freund <andres(at)anarazel(dot)de> |
| Cc: | Thomas Munro <thomas(dot)munro(at)enterprisedb(dot)com>, Ravi Krishna <srkrishna(at)yahoo(dot)com>, "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-19 02:59:49 |
| Message-ID: | CAANVwEu9TOXvDAFGG+zH4H3x-6X0it3KUtBDrn9WHHsTGQR0Vw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
> What do you mean by "not being included by #ifdef blocks"? The only
> guard in issue_xlog_fsync() is #ifdef HAVE_FDATASYNC, which ought to be
> independent of any includes? I can see how this'd go wrong if configure
> did *not* detect fdatasync, because then
>
And now this looks like it works again from a clean build - something
screwy with WSL perhaps? Or me?
Either way, I can't reproduce - annoyingly.
--
The contents of this email are confidential and may be subject to legal or
professional privilege and copyright. No representation is made that this
email is free of viruses or other defects. If you have received this
communication in error, you may not copy or distribute any part of it or
otherwise disclose its contents to anyone. Please advise the sender of your
incorrect receipt of this correspondence.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | James Sewell | 2019-02-19 04:16:19 | Re: WSL (windows subsystem on linux) users will need to turn fsync off as of 11.2 |
| Previous Message | Andres Freund | 2019-02-19 01:06:22 | Re: WSL (windows subsystem on linux) users will need to turn fsync off as of 11.2 |