Received: from localhost (unknown [200.46.204.191]) by postgresql.org (Postfix) with ESMTP id 82AC02E2DE4 for ; Thu, 13 Dec 2007 17:49:56 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.191]) (amavisd-maia, port 10024) with ESMTP id 83492-06 for ; Thu, 13 Dec 2007 17:49:53 -0400 (AST) Received: from main2.mycybernet.net (main2.mycybernet.net [209.222.63.140]) by postgresql.org (Postfix) with ESMTP id C3F0A2E2DC1 for ; Thu, 13 Dec 2007 17:49:53 -0400 (AST) Received: from 227-54-222-209.mycybernet.net ([209.222.54.227] helo=crankycanuck.ca) by main2.mycybernet.net with esmtp (Exim 4.62) (envelope-from ) id 1J2vwG-0008HW-QU for pgsql-admin@postgresql.org; Thu, 13 Dec 2007 16:49:52 -0500 Received: by crankycanuck.ca (Postfix, from userid 1000) id 911605009C; Thu, 13 Dec 2007 16:49:47 -0500 (EST) Date: Thu, 13 Dec 2007 16:49:47 -0500 From: Andrew Sullivan To: pgsql-admin@postgresql.org Subject: Re: Dangerous hint in the PostgreSQL manual Message-ID: <20071213214947.GF7060@crankycanuck.ca> Mail-Followup-To: Andrew Sullivan , pgsql-admin@postgresql.org 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> <20071212164256.GV31954@crankycanuck.ca> <20071212180152.9z7o4rvegww8gkgc@webmail.kwsoft.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20071212180152.9z7o4rvegww8gkgc@webmail.kwsoft.de> User-Agent: Mutt/1.5.13 (2006-08-11) X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200712/98 X-Sequence-Number: 27615 On Wed, Dec 12, 2007 at 06:01:52PM +0100, Listaccount wrote: > BTW : How can one find out the application doing unused allocations? > What value of "ps" output to watch for? As far as I know, the only way to learn that is to use a debugger. If the OS knew this, it'd be able to shoot the misbehaving process instead of whatever it guesses on. A