| From: | Amit Kapila <amit(dot)kapila16(at)gmail(dot)com> |
|---|---|
| To: | Andres Freund <andres(at)anarazel(dot)de> |
| Cc: | Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr>, PostgreSQL Developers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: checkpointer continuous flushing |
| Date: | 2015-10-20 07:35:42 |
| Message-ID: | CAA4eK1J__4RCgbPfTA9jOxW3Nq5GkuBu1jt_-1AhH4E8YM6XMQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Mon, Oct 19, 2015 at 4:06 AM, Andres Freund <andres(at)anarazel(dot)de> wrote:
>
>
> I wonder if mmap() && msync(MS_ASYNC) isn't a better replacement for
> sync_file_range(SYNC_FILE_RANGE_WRITE) than posix_fadvise(DONTNEED). It
> might even be possible to later approximate that on windows using
> FlushViewOfFile().
>
I think this idea is worth exploring especially because we can have
Windows equivalent for this optimisation. Will this option by any
chance can lead to increase in memory usage as mmap has to
map the file/'s?
With Regards,
Amit Kapila.
EnterpriseDB: http://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Amit Kapila | 2015-10-20 08:32:44 | Re: Checkpoint throttling issues |
| Previous Message | Michael Paquier | 2015-10-20 07:25:11 | Re: [RFC] overflow checks optimized away |