X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (av.hub.org [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id C8D8ED7C5F for ; Fri, 26 Aug 2005 05:35:35 -0300 (ADT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 03987-08 for ; Fri, 26 Aug 2005 08:35:34 +0000 (GMT) Received: from mail.metronet.co.uk (mail.metronet.co.uk [213.162.97.75]) by svr1.postgresql.org (Postfix) with ESMTP id 124CFD7C70 for ; Fri, 26 Aug 2005 05:35:31 -0300 (ADT) Received: from mainbox.archonet.com (84-51-143-99.archon037.adsl.metronet.co.uk [84.51.143.99]) by smtp.metronet.co.uk (MetroNet Mail) with ESMTP id 2A54B417C49; Fri, 26 Aug 2005 09:35:27 +0100 (BST) Received: from localhost (localhost.localdomain [127.0.0.1]) by mainbox.archonet.com (Postfix) with ESMTP id 45ABC15EDB; Fri, 26 Aug 2005 09:34:34 +0100 (BST) Received: from mainbox.archonet.com ([127.0.0.1]) by localhost (mainbox [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 31733-01; Fri, 26 Aug 2005 09:34:32 +0100 (BST) Received: from [192.168.1.17] (client17.office.archonet.com [192.168.1.17]) by mainbox.archonet.com (Postfix) with ESMTP id E8FFE15ED9; Fri, 26 Aug 2005 09:34:31 +0100 (BST) Message-ID: <430ED417.2050601@archonet.com> Date: Fri, 26 Aug 2005 09:34:31 +0100 From: Richard Huxton User-Agent: Mozilla Thunderbird 1.0.2 (X11/20050317) X-Accept-Language: en-us, en MIME-Version: 1.0 To: "Chun Yit(Chronos)" Cc: pgsql-performance@postgresql.org Subject: Re: postmaster memory keep going up???? References: <000b01c5aa04$a1ba0100$a279640a@Beh> In-Reply-To: <000b01c5aa04$a1ba0100$a279640a@Beh> Content-Type: text/plain; charset=GB2312 Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.057 required=5 tests=[AWL=0.007, FORGED_RCVD_HELO=0.05] X-Spam-Level: X-Archive-Number: 200508/434 X-Sequence-Number: 14181 Chun Yit(Chronos) wrote: >>I have a pl/pgsql function that using temp table to perform searching logic, >>my question is,it is postmaster have memory leaking problem? First step - upgrade to the latest 7.4.x release. Second step - read the "release notes" section of the manuals for 7.4.x and 8.0.x and see what it says about memory and plpgsql. -- Richard Huxton Archonet Ltd