X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id 4B6033A3D02 for ; Mon, 17 Jan 2005 18:49:18 +0000 (GMT) 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 40620-09 for ; Mon, 17 Jan 2005 18:49:15 +0000 (GMT) Received: from school.digsys.bg (school.digsys.bg [193.68.6.1]) by svr1.postgresql.org (Postfix) with ESMTP id 902BB3A3E0E for ; Mon, 17 Jan 2005 18:49:12 +0000 (GMT) Received: from faith.digsys.bg (sigma.digsys.bg [193.68.6.19]) by school.digsys.bg (8.11.6/8.10.1) with ESMTP id j0HIn1D01349; Mon, 17 Jan 2005 20:49:01 +0200 (EET) Message-ID: <41EC0A86.5090001@faith.digsys.bg> Date: Mon, 17 Jan 2005 20:57:10 +0200 From: Kaloyan Iliev Iliev User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6) Gecko/20040115 X-Accept-Language: en-us, en, bg MIME-Version: 1.0 To: Tom Lane , pgsql-performance@postgresql.org Subject: Re: Performance problem from migrating between versions! References: <41EBDBBB.3070301@faith.digsys.bg> <2253.1105978380@sss.pgh.pa.us> <41EBFDBF.9040105@faith.digsys.bg> <3957.1105985240@sss.pgh.pa.us> In-Reply-To: <3957.1105985240@sss.pgh.pa.us> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.071 tagged_above=0 required=5 tests=AWL, FORGED_RCVD_HELO X-Spam-Level: X-Archive-Number: 200501/213 X-Sequence-Number: 9903 Tom Lane wrote: >I wouldn't recommend turning off hashagg as a permanent solution, it >was just a quickie to verify my suspicion of where the memory was going. > > > Hi, How to understant the upper sentence? I shouldn't turn "hashagg" off permanently for this query or for the entire database. For now I turn it off for this query, so it can work. If I shouldn't, then what should I do? Will ANALYZE resove this? Kaloyan Iliev