X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [64.117.224.130]) by svr1.postgresql.org (Postfix) with ESMTP id 34650D1B524 for ; Thu, 14 Aug 2003 15:21:33 +0000 (GMT) Received: from svr1.postgresql.org ([64.117.224.193]) by localhost (neptune.hub.org [64.117.224.130]) (amavisd-new, port 10024) with ESMTP id 46250-10 for ; Thu, 14 Aug 2003 12:19:52 -0300 (ADT) Received: from sss.pgh.pa.us (unknown [192.204.191.242]) by svr1.postgresql.org (Postfix) with ESMTP id 1AC68D1B4F0 for ; Thu, 14 Aug 2003 12:21:21 -0300 (ADT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.12.9/8.12.9) with ESMTP id h7EFIh5H001579; Thu, 14 Aug 2003 11:18:43 -0400 (EDT) To: Bertrand Petit Cc: pgsql-performance@postgresql.org Subject: Re: 7.4 beta 1 getting out of swap In-reply-to: <20030814165311.A4431@memo.frmug.org> References: <20030814122130.A3583@memo.frmug.org> <15589.1060861546@sss.pgh.pa.us> <20030814165311.A4431@memo.frmug.org> Comments: In-reply-to Bertrand Petit message dated "Thu, 14 Aug 2003 16:53:11 +0200" Date: Thu, 14 Aug 2003 11:18:42 -0400 Message-ID: <1578.1060874322@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200308/258 X-Sequence-Number: 3075 Bertrand Petit writes: > On Thu, Aug 14, 2003 at 07:45:46AM -0400, Tom Lane wrote: >> Please show us the memory context size info that the backend dumps to >> stderr when it reports "out of memory". > Here it is: > ExecutorState: 4556232 total in 46 blocks; 3183264 free (8303 chunks); 1372968 used That seems a bit large, but I'm not sure if it's really to worry about. > ExecutorState: 528474112 total in 72 blocks; 760 free (1 chunks); 528473352 used Okay, you definitely must have a memory leak in query execution. Could you provide enough info to let someone else reproduce it? We don't need your data, but a schema dump (pg_dump -s) would be nice to avoid trying to guess what causes it. regards, tom lane