From: | Andres Freund <andres(at)anarazel(dot)de> |
---|---|
To: | pgsql-committers(at)postgresql(dot)org, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Subject: | Re: pgsql: Allow to trigger kernel writeback after a configurable number of |
Date: | 2016-03-12 06:08:32 |
Message-ID: | 20160312060832.szkhp4srs7vmqgy7@alap3.anarazel.de |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-committers |
Tom,
On 2016-03-11 01:29:09 +0000, Andres Freund wrote:
> Several operating systems allow some control over the kernel page
> cache. Linux has sync_file_range(2), several posix systems have msync(2)
> and posix_fadvise(2). sync_file_range(2) is preferable because it
> requires no special setup, whereas msync() requires the to-be-flushed
> range to be mmap'ed. For the purpose of flushing dirty data
> posix_fadvise(2) is the worst alternative, as flushing dirty data is
> just a side-effect of POSIX_FADV_DONTNEED, which also removes the pages
> from the page cache. Thus the feature is enabled by default only on
> linux, but can be enabled on all systems that have any of the above
> APIs.
This broke gaur:
http://pgbuildfarm.org/cgi-bin/show_log.pl?nm=gaur&dt=2016-03-12%2005%3A44%3A25
I'm planning to add a #ifndef MAP_FAILED #define MAP_FAILED ((void*)
(-1)).
Unless HPPA simply has that defined elsewhere?
Greetings,
Andres Freund
From | Date | Subject | |
---|---|---|---|
Next Message | Amit Kapila | 2016-03-12 07:24:15 | Re: [COMMITTERS] pgsql: Provide much better wait information in pg_stat_activity. |
Previous Message | Joel Jacobson | 2016-03-12 05:54:29 | Re: [COMMITTERS] pgsql: Provide much better wait information in pg_stat_activity. |