From: | Andrew Sullivan <ajs(at)crankycanuck(dot)ca> |
---|---|
To: | pgsql-admin(at)postgresql(dot)org, pgsql-docs(at)postgresql(dot)org |
Subject: | Re: Dangerous hint in the PostgreSQL manual |
Date: | 2007-12-12 16:42:56 |
Message-ID: | 20071212164256.GV31954@crankycanuck.ca |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin pgsql-docs |
Dear docs mavens:
Please see below for a possible adjustment to the docs. Is it agreeable?
If so, I'll see about putting together a patch.
On Wed, Dec 12, 2007 at 05:19:24PM +0100, Listaccount wrote:
> >What I _would_ support in the docs is the following addition in 17.4.3,
> >where this is discussed:
> >
> > . . .it will lower the chances significantly and will therefore
> > lead to more robust system behavior. It may also cause fork() to fail
> > when the machine appears to have available memory. This is done by
> > selecting. . .
> >
> >Or something like that. This would warn potential users that they really
> >do
> >need to read their kernel docs.
>
> On this one we can agree. Maybe we should mention the root-cause.
>
> "It may also cause fork() to fail when the machine appears to have
> available memory because of other applications doing careless memory
> allocation"
>
> Would be nice to save others from learning about this the hard way.
>
> Regards
>
> Andreas
From | Date | Subject | |
---|---|---|---|
Next Message | Listaccount | 2007-12-12 17:01:52 | Re: Dangerous hint in the PostgreSQL manual |
Previous Message | Listaccount | 2007-12-12 16:19:24 | Re: Dangerous hint in the PostgreSQL manual |
From | Date | Subject | |
---|---|---|---|
Next Message | Listaccount | 2007-12-12 17:01:52 | Re: Dangerous hint in the PostgreSQL manual |
Previous Message | Listaccount | 2007-12-12 16:19:24 | Re: Dangerous hint in the PostgreSQL manual |