| From: | Joe Conway <mail(at)joeconway(dot)com> |
|---|---|
| To: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Andrew Sullivan <andrew(at)libertyrms(dot)info>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Experimental patch for inter-page delay in VACUUM |
| Date: | 2003-11-10 05:00:06 |
| Message-ID: | 3FAF1B56.4050204@joeconway.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Bruce Momjian wrote:
> Agreed, we can't resize shared memory, but I don't think most OS's swap
> out shared memory, and even if they do, they usually have a kernel
> configuration parameter to lock it into kernel memory. All the old
> unixes locked the shared memory into kernel address space and in fact
> this is why many of them required a kernel recompile to increase shared
> memory. I hope the ones that have pagable shared memory have a way to
> prevent it --- at least FreeBSD does, not sure about Linux.
I'm pretty sure at least Linux, Solaris, and HPUX all work this way --
otherwise Oracle would have the same problem with their SGA, which is
kept in shared memory.
Joe
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andriy Tkachuk | 2003-11-10 08:58:28 | Re: what could cause this PANIC on enterprise 7.3.4 db? |
| Previous Message | Joe Conway | 2003-11-10 04:54:25 | Re: Experimental patch for inter-page delay in VACUUM |