On Fri, Mar 13, 2009 at 10:06 PM, Tom Lane <t...@sss.pgh.pa.us> wrote: > Gregory Stark <st...@enterprisedb.com> writes: >> Tom Lane <t...@sss.pgh.pa.us> writes: >>> Ugh. So apparently, we actually need to special-case Solaris to not >>> believe that posix_fadvise works, or we'll waste cycles uselessly >>> calling a do-nothing function. Thanks, Sun. > >> Do we? Or do we just document that setting effective_cache_size on Solaris >> won't help? > > I assume you meant effective_io_concurrency. We'd still need a special > case because the default is currently hard-wired at 1, not 0, if > configure thinks the function exists. Also there's a posix_fadvise call > in xlog.c that that parameter doesn't control anyhow.
I think 1 should mean no prefetching, rather than 0. If the number of concurrent I/O requests was 0, that would mean you couldn't perform any I/O at all. ...Robert -- Sent via pgsql-performance mailing list (pgsql-performance@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-performance
