Re: Very strange query difference between 7.3.6 and 7.4.6

Tom Lane wrote:

>"Joshua D. Drake" <jd(at)commandprompt(dot)com> writes:
>
>
>>O.k. I got 7.3.9 to operate as expected on FC2 (64bit) and these are my
>>results:
>>
>>
>
>
>
>>enable_hashagg on:
>>
>>
>
>
>
>> HashAggregate (cost=80.00..82.50 rows=1000 width=404) (actual
>>time=209.746..209.750 rows=1 loops=1)
>>
>>
>
>You got confused somewhere along the line, because 7.3 doesn't have
>hash aggregation ...
>
>
DOH! You are correct. Heh... Anyway here is the real 7.3.9
on FC2 64bit plan:
RY
PLAN

--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Aggregate (cost=69.83..132.33 rows=100 width=404) (actual
time=771.96..771.96 rows=1 loops=1)
-> Group (cost=69.83..129.83 rows=1000 width=404) (actual
time=579.98..767.54 rows=8845 loops=1)
-> Sort (cost=69.83..72.33 rows=1000 width=404) (actual
time=579.96..590.00 rows=8845 loops=1)
Sort Key: post_id, topic_id, topic_title, topic_status,
topic_replies, topic_time, topic_type, topic_vote, topic_last_post_id,
forum_name, forum_status, forum_id, auth_view, auth_read, auth_post,
auth_reply, auth_edit, auth_delete, auth_sticky, auth_announce,
auth_pollcreate, auth_vote, auth_attachments
-> Seq Scan on foo (cost=0.00..20.00 rows=1000
width=404) (actual time=0.05..107.62 rows=8845 loops=1)
Total runtime: 774.57 msec
(6 rows)

> regards, tom lane
>
>---------------------------(end of broadcast)---------------------------
>TIP 1: subscribe and unsubscribe commands go to majordomo(at)postgresql(dot)org
>
>

--
Command Prompt, Inc., home of Mammoth PostgreSQL - S/ODBC and S/JDBC
Postgresql support, programming shared hosting and dedicated hosting.
+1-503-667-4564 - jd(at)commandprompt(dot)com - http://www.commandprompt.com
PostgreSQL Replicator -- production quality replication for PostgreSQL