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:57:10 +0200
Message-ID: <41EC0A86.5090001@faith.digsys.bg> (raw)
In-Reply-To: <3957.1105985240@sss.pgh.pa.us>
References: <41EBDBBB.3070301@faith.digsys.bg>
<2253.1105978380@sss.pgh.pa.us>
<41EBFDBF.9040105@faith.digsys.bg>
<3957.1105985240@sss.pgh.pa.us>
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
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: <41EC0A86.5090001@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