Russell Smith <[EMAIL PROTECTED]> 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
---------------------------(end of broadcast)---------------------------
TIP 3: Have you checked our extensive FAQ?
http://www.postgresql.org/docs/faq
