X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [64.117.224.193]) by svr1.postgresql.org (Postfix) with ESMTP id 0DBA530ED11 for ; Mon, 16 Jun 2003 20:59:29 +0000 (GMT) Received: from svr1.postgresql.org ([64.117.224.193]) by localhost (svr1.postgresql.org [64.117.224.193]) (amavisd-new, port 10024) with ESMTP id 07316-10 for ; Mon, 16 Jun 2003 17:59:18 -0300 (ADT) Received: from smaug.securitymatrix.com (unknown [64.25.5.177]) by svr1.postgresql.org (Postfix) with ESMTP id 30C1A30EF1B for ; Mon, 16 Jun 2003 17:59:18 -0300 (ADT) Received: from kaos.securitymatrix.com ([172.16.0.101]) by smaug.securitymatrix.com (8.11.6/8.11.6) with ESMTP id h5GKwdV21285; Mon, 16 Jun 2003 16:58:40 -0400 Subject: Re: Postgres Connections Requiring Large Amounts of Memory From: Dawn Hollingsworth To: Tom Lane Cc: pgsql-performance@postgresql.org In-Reply-To: <6634.1055796302@sss.pgh.pa.us> References: <1055752337.2182.49.camel@kaos> <6634.1055796302@sss.pgh.pa.us> Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Mailer: Ximian Evolution 1.0.8 Date: 16 Jun 2003 08:57:35 +0000 Message-Id: <1055753856.5467.57.camel@kaos> Mime-Version: 1.0 X-Archive-Number: 200306/100 X-Sequence-Number: 2184 We have just recently hired a database consultant familiar with Postgres and just on his cursory glance we are not doing anything really crazy. There are two things which might be considered off the beaten path though: 1. We have tables that have over 500 columns which we continually insert into and select from. 2. Our stored procedures take more than 16 parameters so in the file config.h the value INDEX_MAX_KEYS was increased to 100. -Dawn On Mon, 2003-06-16 at 20:45, Tom Lane wrote: > Dawn Hollingsworth writes: > > PostgreSQL Version: 7.2.3 > > > My problem is that the memory used by the connections appears to grow > > over time, especially when the amount of data entering the system is > > increased. > > We have fixed memory-leak problems in the past, and I wouldn't be > surprised if some remain, but you'll have to give a lot more detail > about what you're doing if you want help. A leak that persists across > transaction boundaries is fairly surprising --- I think I can safely > say that there are none in the normal code paths. I'm guessing you must > be using some off-the-beaten-path feature. > > regards, tom lane > > ---------------------------(end of broadcast)--------------------------- > TIP 7: don't forget to increase your free space map settings