Received: from localhost (unknown [200.46.204.187]) by postgresql.org (Postfix) with ESMTP id 9B4459FA397 for ; Thu, 11 Oct 2007 22:27:45 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.187]) (amavisd-maia, port 10024) with ESMTP id 71755-01 for ; Thu, 11 Oct 2007 22:26: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 CE92C9FBB1A for ; Thu, 11 Oct 2007 22:27:02 -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 l9C1QxXj015392; Thu, 11 Oct 2007 21:26:59 -0400 (EDT) To: henk de wit cc: "pgsql-performance@postgresql.org" Subject: Re: Huge amount of memory consumed during transaction In-reply-to: References: <13678.1192114295@sss.pgh.pa.us> Comments: In-reply-to henk de wit message dated "Fri, 12 Oct 2007 01:23:33 +0200" Date: Thu, 11 Oct 2007 21:26:59 -0400 Message-ID: <15391.1192152419@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200710/141 X-Sequence-Number: 27163 henk de wit writes: > I'm not exactly sure what to look for in the log. I'll do my best though an= > d see what I can come up with. It'll be a bunch of lines like TopMemoryContext: 49832 total in 6 blocks; 8528 free (6 chunks); 41304 used immediately in front of the out-of-memory ERROR report. regards, tom lane