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 15C153A3DD5 for ; Mon, 17 Jan 2005 17:54:58 +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 32675-03 for ; Mon, 17 Jan 2005 17:54:44 +0000 (GMT) Received: from school.digsys.bg (school.digsys.bg [193.68.6.1]) by svr1.postgresql.org (Postfix) with ESMTP id AB9B93A3D88 for ; Mon, 17 Jan 2005 17:54:42 +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 j0HHsVD01043; Mon, 17 Jan 2005 19:54:31 +0200 (EET) Message-ID: <41EBFDBF.9040105@faith.digsys.bg> Date: Mon, 17 Jan 2005 20:02:39 +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> In-Reply-To: <2253.1105978380@sss.pgh.pa.us> Content-Type: text/plain; charset=windows-1251; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.068 tagged_above=0 required=5 tests=AWL, FORGED_RCVD_HELO X-Spam-Level: X-Archive-Number: 200501/207 X-Sequence-Number: 9897 Thanks, It worked. I have read in the docs what this "enable_hashagg" do, but I couldn't understand it. What does it change? From the Doc: ------- enable_hashagg (boolean) Enables or disables the query planner's use of hashed aggregation plan types. The default is on. This is used for debugging the query planner. -------- How it is used to debug the query planner? And why it lower the mem usage? Thank you in advance. Kaloyan Iliev Tom Lane wrote: >Kaloyan Iliev Iliev writes: > > >>I have the following problem. A week ago we've migrated from PGv7.2.3 to >>7.4.6. There were a lot of things in the apps to chenge but we made >>them. But one query doesn't want to run. In the old PGv7.2.3 it passes >>for 10 min. In the new one it gaves: >>DBD::Pg::st execute failed: ERROR: out of memory >> >> > >Does setting enable_hashagg to OFF fix it? > > regards, tom lane > > > >