Received: from localhost (unknown [200.46.204.184]) by postgresql.org (Postfix) with ESMTP id 28D7E9FBA7F for ; Thu, 11 Oct 2007 14:50:25 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.184]) (amavisd-maia, port 10024) with ESMTP id 18300-05 for ; Thu, 11 Oct 2007 14:49:57 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.5 Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by postgresql.org (Postfix) with ESMTP id 002B29FB929 for ; Thu, 11 Oct 2007 14:49:58 -0300 (ADT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.1/8.14.1) with ESMTP id l9BHnhRF002508; Thu, 11 Oct 2007 13:49:43 -0400 (EDT) To: Erik Jones cc: henk de wit , "pgsql-performance@postgresql.org" Subject: Re: Huge amount of memory consumed during transaction In-reply-to: <69723004-A93C-41DE-BC69-57ABFAB059C2@myemma.com> References: <13678.1192114295@sss.pgh.pa.us> <69723004-A93C-41DE-BC69-57ABFAB059C2@myemma.com> Comments: In-reply-to Erik Jones message dated "Thu, 11 Oct 2007 11:51:08 -0500" Date: Thu, 11 Oct 2007 13:49:43 -0400 Message-ID: <2507.1192124983@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200710/136 X-Sequence-Number: 27158 Erik Jones writes: > Tom, are there any docs anywhere that explain how to interpret those =20 > per-context memory dumps? No, not really. What you have to do is grovel around in the code and see where contexts with particular names might get created. > For example, when I see an autovacuum =20 > context listed is it safe to assume that the error came from an =20 > autovac operation, etc.? Probably, but I haven't looked. regards, tom lane