X-Original-To: pgsql-performance-postgresql.org@postgresql.org Received: from localhost (wm.hub.org [200.46.204.128]) by postgresql.org (Postfix) with ESMTP id 6A49B9FB2FC for ; Thu, 31 Aug 2006 14:54:57 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.128]) (amavisd-new, port 10024) with ESMTP id 10851-05 for ; Thu, 31 Aug 2006 17:54:49 +0000 (UTC) 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 B74359FB210 for ; Thu, 31 Aug 2006 14:54:47 -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 k7VHslVx021865; Thu, 31 Aug 2006 13:54:47 -0400 (EDT) To: "Indika Maligaspe" cc: pgsql-performance@postgresql.org Subject: Re: Postgress memory leak with JBoss3.2.6 and large DB In-reply-to: <20060831095135.4292E9D7@dm17.mta.everyone.net> References: <20060831095135.4292E9D7@dm17.mta.everyone.net> Comments: In-reply-to "Indika Maligaspe" message dated "Thu, 31 Aug 2006 22:22:48 +0530" Date: Thu, 31 Aug 2006 13:54:47 -0400 Message-ID: <21864.1157046887@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200608/493 X-Sequence-Number: 20678 "Indika Maligaspe" writes: > The problem is when we are querying a specific set of table (which all > tables having over 100K of rows), the Postgres user process takes over or > close 700MB of memory. This is just to return 3000 odd rows. Even though we > have lot of data we still do not have that much to eat up this much of > memory. Playing with server-side settings won't have the slightest effect on a client-side problem. I'd suggest asking about this on the pgsql-jdbc list; they are more likely to have useful suggestions than backend hackers will. regards, tom lane