X-Original-To: pgsql-general-postgresql.org@localhost.postgresql.org
Received: from localhost (av.hub.org [200.46.204.144])
	by postgresql.org (Postfix) with ESMTP id B71B89DC85D
	for <pgsql-general-postgresql.org@localhost.postgresql.org>;
	Tue, 13 Dec 2005 13:40:14 -0400 (AST)
Received: from postgresql.org ([200.46.204.71])
	by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024)
	with ESMTP id 57554-02
	for <pgsql-general-postgresql.org@localhost.postgresql.org>;
	Tue, 13 Dec 2005 13:40:09 -0400 (AST)
X-Greylist: from auto-whitelisted by SQLgrey-
Received: from koolancexeon.g2switchworks.com (mail.g2switchworks.com
	[63.87.162.25]) by postgresql.org (Postfix) with ESMTP id EA9AD9DC856
	for <pgsql-general@postgresql.org>;
	Tue, 13 Dec 2005 13:40:06 -0400 (AST)
Received: mail.g2switchworks.com 10.10.1.8 from 10.10.1.37 10.10.1.37 via HTTP
	with MS-WebStorage 6.5.6944
Received: from state.g2switchworks.com by mail.g2switchworks.com;
	13 Dec 2005 11:40:06 -0600
Subject: Re: Memory Leakage Problem
From: Scott Marlowe <smarlowe@g2switchworks.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: John Sidney-Woollett <johnsw@wardbrook.com>,
	pgsql general <pgsql-general@postgresql.org>
In-Reply-To: <6375.1134486792@sss.pgh.pa.us>
References: <c10e7feb0512060122u33a9c8eakb178525f3834b00@mail.gmail.com>
	<1133891282.11803.7.camel@state.g2switchworks.com>
	<c10e7feb0512061816o21305ac7n576694f2624dc6ed@mail.gmail.com>
	<1133991204.11803.43.camel@state.g2switchworks.com>
	<c10e7feb0512071825h30c93c00kdf5ea2a11e613f0b@mail.gmail.com>
	<b918cf3d0512071946m3cbfc630y679e0350a7f6b864@mail.gmail.com>
	<6353.1134016733@sss.pgh.pa.us>
	<b918cf3d0512080600q5c841fc8lecd96c3bad66cfdc@mail.gmail.com>
	<439DDB49.3000905@freedomhealthcare.org>
	<439E7B7A.9080205@wardbrook.com>
	<3666.1134460063@sss.pgh.pa.us> <439E80B1.8030800@wardbrook.com>
	<6375.1134486792@sss.pgh.pa.us>
Content-Type: text/plain
Content-Transfer-Encoding: 7bit
Message-Id: <1134495605.3587.110.camel@state.g2switchworks.com>
Mime-Version: 1.0
X-Mailer: Ximian Evolution 1.4.6 (1.4.6-2) 
Date: Tue, 13 Dec 2005 11:40:06 -0600
X-Virus-Scanned: by amavisd-new at hub.org
X-Spam-Status: No, score=0.001 required=5 tests=[UNPARSEABLE_RELAY=0.001]
X-Spam-Score: 0.001
X-Spam-Level: 
X-Archive-Number: 200512/651
X-Sequence-Number: 88214

On Tue, 2005-12-13 at 09:13, Tom Lane wrote:
> John Sidney-Woollett <johnsw@wardbrook.com> writes:
> > Tom Lane wrote:
> >> *What* is consuming memory, exactly --- which processes?
> 
> > Sorry but I don't know how to determine that.
> 
> Try "ps auxw", or some other incantation if you prefer, so long as it
> includes some statistics about process memory use.  What you showed us
> is certainly not helpful.

Or run top and hit M while it's running, and it'll sort according to
what uses the most memory.