pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Kaloyan Iliev Iliev <news1@faith.digsys.bg>
To: Tom Lane <tgl@sss.pgh.pa.us>
To: pgsql-performance@postgresql.org
Subject: Re: Performance problem from migrating between versions!
Date: Mon, 17 Jan 2005 20:02:39 +0200
Message-ID: <41EBFDBF.9040105@faith.digsys.bg> (raw)
In-Reply-To: <2253.1105978380@sss.pgh.pa.us>
References: <41EBDBBB.3070301@faith.digsys.bg>
	<2253.1105978380@sss.pgh.pa.us>

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 <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
>
>
>  
>



view thread (8+ messages)  latest in thread

Message-ID: <41EBFDBF.9040105@faith.digsys.bg>
Permalink:  ../41EBFDBF.9040105@faith.digsys.bg/
Also on:    postgresql.org/message-id/41EBFDBF.9040105@faith.digsys.bg

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-performance@postgresql.org
  Cc: news1@faith.digsys.bg, tgl@sss.pgh.pa.us
  Subject: Re: Performance problem from migrating between versions!
  In-Reply-To: <41EBFDBF.9040105@faith.digsys.bg>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox