Received: from localhost (unknown [200.46.204.187]) by postgresql.org (Postfix) with ESMTP id 48F992E0380 for ; Tue, 11 Dec 2007 10:08:43 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.187]) (amavisd-maia, port 10024) with ESMTP id 33650-10 for ; Tue, 11 Dec 2007 10:08:32 -0400 (AST) Received: from mailin.kwsoft.de (mailin.kwsoft.de [213.164.67.82]) by postgresql.org (Postfix) with ESMTP id 4C66D2E0147 for ; Tue, 11 Dec 2007 10:08:38 -0400 (AST) Received: from localhost (localhost [127.0.0.1]) by mailin.kwsoft.de (Postfix) with ESMTP id CDF697D21F for ; Tue, 11 Dec 2007 15:08:36 +0100 (CET) Received: from mailer.kwsoft.de (mailer.kwsoft.de [10.5.0.1]) by webmail.kwsoft.de (Horde MIME library) with HTTP; Tue, 11 Dec 2007 15:08:36 +0100 Message-ID: <20071211150836.00ql03638kok48s0@webmail.kwsoft.de> Date: Tue, 11 Dec 2007 15:08:36 +0100 From: Listaccount To: pgsql-admin@postgresql.org Subject: Re: Dangerous hint in the PostgreSQL manual References: <20071210162612.a9y113hzjkookooc@webmail.kwsoft.de> <20071210204750.GA22340@crankycanuck.ca> <20071211092338.3vsx57ymsswsckw0@webmail.kwsoft.de> <20071211134231.GL26741@crankycanuck.ca> In-Reply-To: <20071211134231.GL26741@crankycanuck.ca> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; DelSp="Yes"; format="flowed" Content-Disposition: inline Content-Transfer-Encoding: quoted-printable User-Agent: Internet Messaging Program (IMP) H3 (4.1.5) X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200712/51 X-Sequence-Number: 27568 Zitat von Andrew Sullivan : > On Tue, Dec 11, 2007 at 09:23:38AM +0100, Listaccount wrote: >> I don't want to start the discussion what is the rigth thing todo, > > Then you shouldn't ask here. The manual was changed to say what it does > after considerable community discussion. In my view, the Linux kernel's > behaviour is completely unacceptable, and exactly the sort of amateur desi= gn > foolishness that people are complaining about when they say Linux is a toy= . It was not a question but a hint how to improve the documentation. It =20 is nice you have a strong opinion on the technical details behind it =20 but one should not include advices without pointing out possible =20 downsides. If this is not possible then the advice should be removed completely =20 because it has nothing to do with PostgreSQL but with shortcomings of =20 the Linux (or some other) Kernel. I would have not been surprised if the OOM-Killer would go around in =20 case of short memory but i was surprised to see fork failed with a =20 system having 1GB Memory available. That's all my own opinion and nothing need to be said anymore. If the =20 maintainer of the docu agree they could take it out or improve if not =20 i don't care because i have learned my lesson but others may suffer =20 from the same hidden problem. Regards Andreas