X-Original-To: pgsql-performance-postgresql.org@postgresql.org Received: from localhost (mx1.hub.org [200.46.208.251]) by postgresql.org (Postfix) with ESMTP id 068349FA5BA for ; Thu, 15 Jun 2006 12:34:52 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.208.251]) (amavisd-new, port 10024) with ESMTP id 09509-07 for ; Thu, 15 Jun 2006 12:34:42 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey- Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by postgresql.org (Postfix) with ESMTP id 20AFE9F9CAA for ; Thu, 15 Jun 2006 12:34:41 -0300 (ADT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.13.6/8.13.6) with ESMTP id k5FFYdLO028322; Thu, 15 Jun 2006 11:34:39 -0400 (EDT) To: "jody brownell" cc: pgsql-performance@postgresql.org Subject: Re: Postgres consuming way too much memory??? In-reply-to: <200606151202.50939.jody.brownell@q1labs.com> References: <200606141618.37849.jody.brownell@q1labs.com> <200606150901.19201.jody.brownell@q1labs.com> <200606150915.10306.jody.brownell@q1labs.com> <200606151202.50939.jody.brownell@q1labs.com> Comments: In-reply-to "jody brownell" message dated "Thu, 15 Jun 2006 12:02:50 -0300" Date: Thu, 15 Jun 2006 11:34:39 -0400 Message-ID: <28321.1150385679@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200606/305 X-Sequence-Number: 19662 "jody brownell" writes: > When postgresql starts to go into this bloating state, I can only make it happen from my java app. That's interesting. The JDBC driver uses protocol features that aren't used by psql, so it's possible that the leak is triggered by one of those features. I wouldn't worry too much about duplicating the problem from psql anyway --- a Java test case will do fine. > I am going to try closing the connection after each TX to see if this > resolves it for now. If not, I will write a java app, stored procedure > (table etc) reproduce it without our application. Even if that works around it for you, please pursue getting a test case together so we can find and fix the underlying problem. regards, tom lane