Added to TODO:
> * Add Intimate Shared Memory(ISM) for Solaris > * Add documentation to lock shared memory into RAM for each OS, if possible I have re-requested the Solaris patch for ISM. --------------------------------------------------------------------------- Tom Lane wrote: > Bruce Momjian <[EMAIL PROTECTED]> writes: > > The attached email shows that Solaris benefits from the ISM or Intimate > > Shared Memory setting during shmat() shared memory creation. It causes > > processes mapping the same shared memory to shared mapping pages _and_ > > locks the pages in RAM. > > Huh? I understand "locks the pages in RAM" but I don't understand the > first part of that. ISTM shared memory is shared memory; if we didn't > share it without this flag, we'd not be working at all on Solaris. > > > I know many OS's lock shared memory in RAM anyway, or have OS parameters > > that control this (FreeBSD), but it seems Solaris does this on a per > > shmat() basis. Should we add this flag to shmat() calls for Solaris? > > Certainly on any OS where we can request pinning our shmem in RAM, we > should do so --- I've pointed out before that allowing our disk buffers > to be swapped out can't be anything but counterproductive. Not sure > that this should be thought of as an "#ifdef SOLARIS" kind of change; > do any other Unixen share this aspect of the API? > > regards, tom lane > > ---------------------------(end of broadcast)--------------------------- > TIP 5: Have you checked our extensive FAQ? > > http://www.postgresql.org/users-lounge/docs/faq.html > -- Bruce Momjian | http://candle.pha.pa.us [EMAIL PROTECTED] | (610) 853-3000 + If your life is a hard drive, | 830 Blythe Avenue + Christ can be your backup. | Drexel Hill, Pennsylvania 19026 ---------------------------(end of broadcast)--------------------------- TIP 5: Have you checked our extensive FAQ? http://www.postgresql.org/users-lounge/docs/faq.html
