From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
---|---|
To: | Greg Stark <gsstark(at)mit(dot)edu> |
Cc: | Alvaro Herrera <alvherre(at)dcc(dot)uchile(dot)cl>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "Jeroen T(dot) Vermeulen" <jtv(at)xs4all(dot)nl>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Pre-allocation of shared memory ... |
Date: | 2003-06-13 02:11:39 |
Message-ID: | 200306130211.h5D2Bdp27886@candle.pha.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Greg Stark wrote:
> I suspect this was less of an issue in the days before copy on write because
> vfork was more widely used/implemented. I'm not sure linux even implements
> vfork other than just as a wrapper around fork. Even BSD ditched it a while
> back though I think I saw that NetBSD reimplemented it since then.
>
> > But then there's the problem of people running database servers on
> > misconfigured machines. They should know better than not setting enough
> > swap space, IMHO anyway.
>
> Well, I've seen DBAs say "Since I don't want the database swapping anyways,
> I'll make really sure it doesn't swap by just not giving it any swap space --
> that's why we bought so much RAM in the first place". It's not obvious that
> you need swap to back memory the machine doesn't even report as being in
> use...
I see no reason RAM can't be used as backing store for possible
copy-on-write use.
--
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup. | Newtown Square, Pennsylvania 19073
From | Date | Subject | |
---|---|---|---|
Next Message | Ron Mayer | 2003-06-13 02:22:14 | Re: Pre-allocation of shared memory ... |
Previous Message | Bruce Momjian | 2003-06-13 02:10:02 | Re: Pre-allocation of shared memory ... |