On Tue, Jul 3, 2012 at 11:36 AM, Andres Freund <and...@2ndquadrant.com> wrote: > Btw, RhodiumToad/Andrew Gierth on irc talked about a reason why sysv shared > memory might be advantageous on some platforms. E.g. on freebsd there is the > kern.ipc.shm_use_phys setting which prevents paging out shared memory and also > seems to make tlb translation cheaper. There does not seem to exist an > alternative for anonymous mmap. > So maybe we should make that a config option?
Yeah, I was noticing some notes to that effect in the documentation this morning. I think the alternative for anonymous mmap is mlock(). However, that can hit kernel limits of its own. I'm not sure what the best thing to do about this is. I think most users will want mlock... but maybe not all? So we end up with one option for whether to use mlock and another for whether to use more or less System V shm? Sounds confusing. -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
