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 7BEEF30E35D for ; Mon, 16 Jun 2003 20:45:15 +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 85798-05 for ; Mon, 16 Jun 2003 17:45:05 -0300 (ADT) Received: from sss.pgh.pa.us (unknown [192.204.191.242]) by svr1.postgresql.org (Postfix) with ESMTP id 8E29930EEF2 for ; Mon, 16 Jun 2003 17:45:04 -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 h5GKj3U6006635; Mon, 16 Jun 2003 16:45:03 -0400 (EDT) To: Dawn Hollingsworth Cc: pgsql-performance@postgresql.org Subject: Re: Postgres Connections Requiring Large Amounts of Memory In-reply-to: <1055752337.2182.49.camel@kaos> References: <1055752337.2182.49.camel@kaos> Comments: In-reply-to Dawn Hollingsworth message dated "16 Jun 2003 08:32:17 -0000" Date: Mon, 16 Jun 2003 16:45:02 -0400 Message-ID: <6634.1055796302@sss.pgh.pa.us> From: Tom Lane X-Archive-Number: 200306/99 X-Sequence-Number: 2183 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