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 53D18D1DCF5 for ; Sun, 18 Apr 2004 12:39:14 -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 62249-05 for ; Sun, 18 Apr 2004 12:39:13 -0300 (ADT) Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by svr1.postgresql.org (Postfix) with ESMTP id 65CF0D1DCC0 for ; Sun, 18 Apr 2004 12:39:12 -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 i3IFdApS019682; Sun, 18 Apr 2004 11:39:10 -0400 (EDT) To: Dennis Bjorklund Cc: "Jim C. Nasby" , pgsql-performance@postgresql.org Subject: Re: Horribly slow hash join In-reply-to: References: Comments: In-reply-to Dennis Bjorklund message dated "Sun, 18 Apr 2004 08:18:47 +0200" Date: Sun, 18 Apr 2004 11:39:10 -0400 Message-ID: <19681.1082302750@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200404/243 X-Sequence-Number: 6543 Dennis Bjorklund writes: > On Sat, 17 Apr 2004, Tom Lane wrote: >> *some* set of inputs. (Also, I have been harboring some notions of >> supporting cross-type hash joins for integer types, which will not work >> unless small int8 values hash the same as int4 etc.) > The simple solution would be to always extend integers to 64 bits (or > whatever the biggest integer is) before calculating the hash. That creates portability issues though. We do not depend on there being a 64-bit-int type for anything except int8 itself, and I don't want to start doing so. regards, tom lane