Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1WLvJ6-0001Kq-O1 for pgsql-hackers@arkaria.postgresql.org; Fri, 07 Mar 2014 13:59:24 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.80) (envelope-from ) id 1WLvJ6-00024U-2W for pgsql-hackers@arkaria.postgresql.org; Fri, 07 Mar 2014 13:59:24 +0000 Received: from makus.postgresql.org ([2001:4800:7903:4::125]) by malur.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1WLvJ3-00024J-M3 for pgsql-hackers@postgresql.org; Fri, 07 Mar 2014 13:59:21 +0000 Received: from smtp-outbound-1.vmware.com ([208.91.2.12]) by makus.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1WLvIz-0001tf-A0 for pgsql-hackers@postgresql.org; Fri, 07 Mar 2014 13:59:19 +0000 Received: from sc9-mailhost1.vmware.com (sc9-mailhost1.vmware.com [10.113.161.71]) by smtp-outbound-1.vmware.com (Postfix) with ESMTP id D54AE284F8; Fri, 7 Mar 2014 05:59:15 -0800 (PST) Received: from zcs-prod-ext-mta-2.vmware.com (zcs-prod-ext-mta-2.vmware.com [10.113.62.224]) by sc9-mailhost1.vmware.com (Postfix) with ESMTP id D19E618433; Fri, 7 Mar 2014 05:59:15 -0800 (PST) Received: from zcs-prod-ext-mta-2.vmware.com (localhost.localdomain [127.0.0.1]) by zcs-prod-ext-mta-2.vmware.com (Postfix) with ESMTP id 2E093C005D; Fri, 7 Mar 2014 05:59:13 -0800 (PST) Received: from [192.168.1.90] (zimbra-prod-ext-proxy-vip.vmware.com [10.113.63.87]) by zcs-prod-ext-mta-2.vmware.com (Postfix) with ESMTPSA; Fri, 7 Mar 2014 05:59:11 -0800 (PST) Message-ID: <5319D0B0.7030908@vmware.com> Date: Fri, 07 Mar 2014 15:59:12 +0200 From: Heikki Linnakangas Organization: VMware User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20131103 Icedove/17.0.10 MIME-Version: 1.0 To: Robert Haas CC: Greg Stark , Tan Tran , PostgreSQL-development Subject: Re: GSoC on WAL-logging hash indexes References: <54977A8C-4AF5-4BCC-B021-78E9CA978077@gmail.com> <531873E8.6050802@vmware.com> <531992AF.2080306@vmware.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Pg-Spam-Score: -6.9 (------) 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 On 03/07/2014 03:48 PM, Robert Haas wrote: >> >So, there seems to be a few fairly simple and independent improvements to be >> >made: >> > >> >1. Replace the heavy-weight lock with pin & vacuum-lock. >> >2. Make it crash-safe, by adding WAL-logging >> >3. Only acquire the exclusive-lock (vacuum-lock after step 1) in VACUUM for >> >the squeeze phase. >> >4. Cache the metapage. >> > >> >We still don't know if it's going to be any better than B-tree after all >> >that's done, but the only way to find out is to go ahead and implement it. > I'm of the opinion that we ought to start by making splits and > vacuuming more concurrent, and then do that stuff. Priorities are a matter of opinion, but note that for many applications the concurrency of splits and vacuuming is pretty much irrelevant (at least after we do bullet point 3 above). Like, if the index is mostly read-only, or at least doesn't grow much. You'd still want it to be crash-safe (2), and you might care a lot about the performance of scans (1 and 4), but if splits and vacuum hold an exclusive lock for a few seconds, that's OK if you only need to do it once in a blue moon. - Heikki -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers