Re: Dangerous hint in the PostgreSQL manual - Mailing list pgsql-admin

From Andrew Sullivan
Subject Re: Dangerous hint in the PostgreSQL manual
Date
Msg-id 20071212164256.GV31954@crankycanuck.ca
Whole thread Raw
In response to Re: Dangerous hint in the PostgreSQL manual  (Listaccount <lst_hoe01@kwsoft.de>)
Responses Re: Dangerous hint in the PostgreSQL manual  (Listaccount <lst_hoe01@kwsoft.de>)
List pgsql-admin
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

pgsql-admin by date:

Previous
From: Listaccount
Date:
Subject: Re: Dangerous hint in the PostgreSQL manual
Next
From: Listaccount
Date:
Subject: Re: Dangerous hint in the PostgreSQL manual