From: | Kaloyan Iliev Iliev <news1(at)faith(dot)digsys(dot)bg> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-performance(at)postgresql(dot)org |
Subject: | Re: Performance problem from migrating between versions! |
Date: | 2005-01-17 18:02:39 |
Message-ID: | 41EBFDBF.9040105@faith.digsys.bg |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
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(at)faith(dot)digsys(dot)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
>
>
>
>
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2005-01-17 18:07:20 | Re: Performance problem from migrating between versions! |
Previous Message | Adrian Holovaty | 2005-01-17 17:59:24 | Re: Index on a function and SELECT DISTINCT |