| From: | Andres Freund <andres(at)anarazel(dot)de> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Bruce Klein <brucek(at)gmail(dot)com>,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 17:49:56 |
| Message-ID: | 8B8CCA3A-83AF-43BA-A773-9C4160BF866E@anarazel.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On February 15, 2019 9:44:50 AM PST, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>Andres Freund <andres(at)anarazel(dot)de> writes:
>> On February 15, 2019 9:13:10 AM PST, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
>wrote:
>>> I'm of the opinion that we shouldn't be panicking for
>sync_file_range
>>> failure, period.
>
>> With some flags it's strictly required, it does"eat"errors depending
>on the flags. So I'm not sure I understand?
>
>Really? The specification says that it starts I/O, not that it waits
>around for any to finish.
That depends on the flags you pass in. By memory I don't think it eats an error with our flags in recent kernels, but I'm not sure.
Andres
--
Sent from my Android device with K-9 Mail. Please excuse my brevity.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Adrian Klaver | 2019-02-15 18:05:34 | Re: PostgreSql Version Compatibility With Apache ActiveMQ |
| Previous Message | Tom Lane | 2019-02-15 17:44:50 | Re: WSL (windows subsystem on linux) users will need to turn fsync off as of 11.2 |