From: Andrew Sullivan <ajs@crankycanuck.ca>
To: pgsql-admin@postgresql.org
To: pgsql-docs@postgresql.org
Subject: Re: Dangerous hint in the PostgreSQL manual
Date: Wed, 12 Dec 2007 11:42:56 -0500
Message-ID: <20071212164256.GV31954@crankycanuck.ca> (raw)
In-Reply-To: <20071212171924.uir6apjasoog00c4@webmail.kwsoft.de>
References: <20071210162612.a9y113hzjkookooc@webmail.kwsoft.de>
<20071210204750.GA22340@crankycanuck.ca>
<20071211092338.3vsx57ymsswsckw0@webmail.kwsoft.de>
<20071211134231.GL26741@crankycanuck.ca>
<20071211150836.00ql03638kok48s0@webmail.kwsoft.de>
<20071211162229.GD27409@crankycanuck.ca>
<20071212171924.uir6apjasoog00c4@webmail.kwsoft.de>
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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-docs@postgresql.org
Cc: ajs@crankycanuck.ca, pgsql-admin@postgresql.org
Subject: Re: Dangerous hint in the PostgreSQL manual
In-Reply-To: <20071212164256.GV31954@crankycanuck.ca>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox