X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.2]) by svr1.postgresql.org (Postfix) with ESMTP id 8036CD1E0D8 for ; Fri, 16 Apr 2004 14:05:02 -0300 (ADT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (neptune.hub.org [200.46.204.2]) (amavisd-new, port 10024) with ESMTP id 97634-08 for ; Fri, 16 Apr 2004 14:04:56 -0300 (ADT) Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by svr1.postgresql.org (Postfix) with ESMTP id 4C980D1DB0A for ; Fri, 16 Apr 2004 14:04:59 -0300 (ADT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.12.11/8.12.11) with ESMTP id i3GH4wk7000809; Fri, 16 Apr 2004 13:04:58 -0400 (EDT) To: "Jim C. Nasby" Cc: pgsql-performance@postgresql.org Subject: Re: Horribly slow hash join In-reply-to: <20040416164644.GH87362@nasby.net> References: <20040416154502.GF87362@nasby.net> <450.1082133251@sss.pgh.pa.us> <20040416164644.GH87362@nasby.net> Comments: In-reply-to "Jim C. Nasby" message dated "Fri, 16 Apr 2004 11:46:44 -0500" Date: Fri, 16 Apr 2004 13:04:58 -0400 Message-ID: <808.1082135098@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200404/219 X-Sequence-Number: 6519 "Jim C. Nasby" writes: > Combined with the hash aggregate problem I saw (see my other email to > the list), do you think there could be some issue with the performance > of the hash function on FreeBSD 5.2 on AMD64? Yeah, I was wondering about that too. Hard to imagine what though. The hash function should be pretty platform-independent. regards, tom lane