X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (av.hub.org [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id D8FBFD86BE for ; Tue, 30 Aug 2005 17:20:27 -0300 (ADT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 57513-01 for ; Tue, 30 Aug 2005 20:20:18 +0000 (GMT) Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by svr1.postgresql.org (Postfix) with ESMTP id 610CDD864B for ; Tue, 30 Aug 2005 17:20:12 -0300 (ADT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.13.1/8.13.1) with ESMTP id j7UKK37g024392; Tue, 30 Aug 2005 16:20:03 -0400 (EDT) To: "Jim C. Nasby" Cc: Scott Marlowe , RAJU kumar , pgsql-admin@postgresql.org Subject: Re: Hash index In-reply-to: <20050830201738.GD77007@pervasive.com> References: <20050826105950.23187.qmail@webmail18.rediffmail.com> <1125428023.28179.94.camel@state.g2switchworks.com> <24115.1125430346@sss.pgh.pa.us> <20050830201738.GD77007@pervasive.com> Comments: In-reply-to "Jim C. Nasby" message dated "Tue, 30 Aug 2005 15:17:38 -0500" Date: Tue, 30 Aug 2005 16:20:03 -0400 Message-ID: <24391.1125433203@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.006 required=5 tests=[AWL=0.006] X-Spam-Level: X-Archive-Number: 200508/398 X-Sequence-Number: 18717 "Jim C. Nasby" writes: > So does that mean a hash index could (theoretically) improve the > performance of a hash join or hash aggregation? I don't think so --- the whole point of a hash is to do your matching in-memory, rather than jumping all over the disk for it ... regards, tom lane