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 B15D33A3DF9 for ; Mon, 17 Jan 2005 18:07:42 +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 34147-06 for ; Mon, 17 Jan 2005 18:07:31 +0000 (GMT) Received: from school.digsys.bg (school.digsys.bg [193.68.6.1]) by svr1.postgresql.org (Postfix) with ESMTP id B4C9E3A3DC5 for ; Mon, 17 Jan 2005 18:07:30 +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 j0HI7MD01153; Mon, 17 Jan 2005 20:07:22 +0200 (EET) Message-ID: <41EC00C3.2040608@faith.digsys.bg> Date: Mon, 17 Jan 2005 20:15:31 +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: multipart/alternative; boundary="------------090402010803010000010803" X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.133 tagged_above=0 required=5 tests=AWL, FORGED_RCVD_HELO, HTML_40_50, HTML_MESSAGE, HTML_TITLE_EMPTY X-Spam-Level: X-Archive-Number: 200501/210 X-Sequence-Number: 9900 This is a multi-part message in MIME format. --------------090402010803010000010803 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Hi, I am asking the prev. question because there is no change in the query plan (as far as I see) but the mem usage decreases from 258M to 16M. 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 > > > > --------------090402010803010000010803 Content-Type: text/html; charset=us-ascii Content-Transfer-Encoding: 7bit Hi,

I am asking the prev. question because there is no change in the query plan (as far as I see) but the mem usage decreases from 258M to 16M.

Kaloyan Iliev

Tom Lane wrote:
Kaloyan Iliev Iliev <news1@faith.digsys.bg> 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


  
--------------090402010803010000010803--