Re: ATTN: Clodaldo was Performance problem. Could it be related to 8.3-beta4?

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Russell Smith <mr-russ(at)pws(dot)com(dot)au>
Cc: PostgreSQL - General ML <pgsql-general(at)postgresql(dot)org>, clodoaldo(dot)pinto(dot)neto(at)gmail(dot)com
Subject: Re: ATTN: Clodaldo was Performance problem. Could it be related to 8.3-beta4?
Date: 2008-01-20 18:05:27
Message-ID: 10135.1200852327@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Russell Smith <mr-russ(at)pws(dot)com(dot)au> writes:
> Tom Lane wrote:
>> A possibly usable workaround for now is "set enable_hashagg = off"
>> to force a GroupAggregate plan, which will deliver the values sorted
>> by (data, usuario) rather than by their hash values.

> If you add ORDER BY to the query, do you get different results?

Yeah, that should have the same effect. An advantage is that you don't
risk clobbering the performance of other queries by mistakenly leaving
hashagg turned off.

regards, tom lane

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Martijn van Oosterhout 2008-01-20 18:06:49 Re: [GENERAL] SHA1 on postgres 8.3
Previous Message Joshua D. Drake 2008-01-20 18:04:17 Re: Sun acquires MySQL