Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1WfYpV-0004po-Mo for pgsql-advocacy@arkaria.postgresql.org; Wed, 30 Apr 2014 18:02:01 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.80) (envelope-from ) id 1WfYpU-0001sf-RG for pgsql-advocacy@arkaria.postgresql.org; Wed, 30 Apr 2014 18:02:00 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1WfYpT-0001sU-UW; Wed, 30 Apr 2014 18:02:00 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by magus.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1WfYpR-0002yA-0J; Wed, 30 Apr 2014 18:01:59 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.4/8.14.4) with ESMTP id s3UI1piJ025059; Wed, 30 Apr 2014 14:01:52 -0400 From: Tom Lane To: Robert Haas cc: Peter Geoghegan , "ktm@rice.edu" , Tan Tran , Greg Stark , pgsql-advocacy , PostgreSQL-development Subject: Re: [HACKERS] GSoC on WAL-logging hash indexes In-reply-to: References: <54977A8C-4AF5-4BCC-B021-78E9CA978077@gmail.com> <20140430125544.GG5746@aart.rice.edu> Comments: In-reply-to Robert Haas message dated "Wed, 30 Apr 2014 13:11:55 -0400" Date: Wed, 30 Apr 2014 14:01:51 -0400 Message-ID: <25058.1398880911@sss.pgh.pa.us> X-Pg-Spam-Score: -2.6 (--) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-advocacy Precedence: bulk Sender: pgsql-advocacy-owner@postgresql.org Robert Haas writes: > I thought the theoretical advantage of hash indexes wasn't that they > were smaller but that you avoided a central contention point (the > btree root). > Of course our current hash indexes have *more* not less contention > than btree but I'm pretty comfortable chalking that up to quality of > implementation rather than anything intrinsic. The long and the short of it is that there are *lots* of implementation deficiences in our hash indexes. There's no real way to know whether they'd be competitive if all those things were rectified, except by doing the work to fix 'em. And it's hard to justify putting much effort into hash indexes so long as there's an elephant in the room of the size of "no WAL support". So I'm in favor of getting that fixed, if we have somebody who's willing to do it. It might lead to good things later; and even if it doesn't, the lack of WAL support is an embarrassment. regards, tom lane -- Sent via pgsql-advocacy mailing list (pgsql-advocacy@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-advocacy