Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1WfcGl-0004m1-O3 for pgsql-hackers@arkaria.postgresql.org; Wed, 30 Apr 2014 21:42:23 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.80) (envelope-from ) id 1WfcGk-00053Y-Vi for pgsql-hackers@arkaria.postgresql.org; Wed, 30 Apr 2014 21:42:23 +0000 Received: from makus.postgresql.org ([2001:4800:7903:4::125]) by malur.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1WfcGj-00053P-J1 for pgsql-hackers@postgresql.org; Wed, 30 Apr 2014 21:42:21 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by makus.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1WfcGh-0005WK-CI for pgsql-hackers@postgresql.org; Wed, 30 Apr 2014 21:42:20 +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 s3ULfvCo029534; Wed, 30 Apr 2014 17:41:57 -0400 From: Tom Lane To: Greg Stark cc: Peter Geoghegan , Jeff Janes , Robert Haas , Tan Tran , PostgreSQL-development Subject: Re: GSoC on WAL-logging hash indexes In-reply-to: References: <54977A8C-4AF5-4BCC-B021-78E9CA978077@gmail.com> Comments: In-reply-to Greg Stark message dated "Wed, 30 Apr 2014 20:16:53 +0100" Date: Wed, 30 Apr 2014 17:41:57 -0400 Message-ID: <29533.1398894117@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-hackers Precedence: bulk Sender: pgsql-hackers-owner@postgresql.org Greg Stark writes: > But imnsho doing nothing is a bad idea. We should have long ago either > added WAL logging or removed the index type. We shouldn't have left a > foot-gun that large lying around for so long. We can't remove the hash index type, nor move it to an extension, because it is the operator classes for the built-in hash index AM that tell the planner and executor how to do hashing for arbitrary datatypes. And we certainly do not want to give up hashing-based query plans, whatever you may think of hash indexes. We really oughta fix the WAL situation, not just band-aid around it. regards, tom lane -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers