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 84B7A9FB29A for ; Tue, 5 Sep 2006 01:01:15 -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 09210-04 for ; Tue, 5 Sep 2006 04:01:02 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey- Received: from omta14.mta.everyone.net (sitemail2.everyone.net [216.200.145.36]) by postgresql.org (Postfix) with ESMTP id C55809FB283 for ; Tue, 5 Sep 2006 01:00:59 -0300 (ADT) Received: from dm21.mta.everyone.net (bigiplb-dsnat [172.16.0.19]) by omta14.mta.everyone.net (Postfix) with ESMTP id CA79A404F7; Mon, 4 Sep 2006 21:00:58 -0700 (PDT) X-Eon-Dm: dm21 Received: by dm21.mta.everyone.net (EON-AUTHRELAY2 - cbbd48ba) id dm21.44f8bfc6.3b126; Mon, 4 Sep 2006 21:00:57 -0700 X-Eon-Sig: AQJKldRE/PZ50wCxQAIAAAAC,f9e35b327b00aee07ec1c3175efd04c4 From: "Indika Maligaspe" To: "'Mark Kirkwood'" , Subject: Re: Postgress memory leak with JBoss3.2.6 and large DB Date: Tue, 5 Sep 2006 09:32:04 +0530 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook, Build 11.0.5510 Thread-Index: AcbP1czx4+KcUF+DTdScTiPuN75qOAAyXVzA X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2869 In-Reply-To: <44FBA332.8020104@paradise.net.nz> Message-Id: <20060904210058.6BAD4ECF@dm21.mta.everyone.net> X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0 tagged_above=0 required=5 tests= X-Spam-Level: X-Archive-Number: 200609/28 X-Sequence-Number: 20714 Hi Guys, We found the issue regarding our memory leak. It was the query. It seams were using functions with fetch cursors on large data sets and the cursors were not getting closed properly. Hence the memory was building up. So I guess this was an application error. In fact we bought the Query memory from 1.4 GB to 2 MB......... Thanks for all the help guys. Because by reading all your comments I was able to understand a lot about Postgres memory settings. K.Indika Maligaspe -----Original Message----- From: pgsql-performance-owner@postgresql.org [mailto:pgsql-performance-owner@postgresql.org] On Behalf Of Mark Kirkwood Sent: Monday, September 04, 2006 9:23 AM To: pgsql-performance@postgresql.org Subject: Re: [PERFORM] Postgress memory leak with JBoss3.2.6 and large DB Indika Maligaspe wrote: > Hey guys, > > We are running a Linux 2.4 enterprise edition box with 6GB of RAM, > **Postgres 8.0.3**. (snippage) > You might want to consider upgrading to 8.0.8 (see below), and seeing if the problem still persists. > As you can see the postmaster users are taking way over the memory that > should be taken. > > > If any of you can give us some pointers we would really appreciate that > and thanks in advance. > I notice that there are a number of fixes for memory leaks since 8.0.3 - 8.0.4 and 8.0.8 is where I see 'em specifically (reading release notes for 8.0.8). So you may be experiencing an issue that is fixed in the current 8.0 releases! I recommend upgrading to 8.0.8. You didn't say what your HW was, but if you are on a 32-bit platform, then a 2.4 kernel when you have >2G ram may leak noticeable amounts of memory itself... Cheers Mark ---------------------------(end of broadcast)--------------------------- TIP 4: Have you searched our list archives? http://archives.postgresql.org