Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1WLvMP-0001T5-O3 for pgsql-hackers@arkaria.postgresql.org; Fri, 07 Mar 2014 14:02:49 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.80) (envelope-from ) id 1WLvMP-0003Vr-8J for pgsql-hackers@arkaria.postgresql.org; Fri, 07 Mar 2014 14:02:49 +0000 Received: from makus.postgresql.org ([2001:4800:7903:4::125]) by malur.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1WLvMO-0003Vj-5z for pgsql-hackers@postgresql.org; Fri, 07 Mar 2014 14:02:48 +0000 Received: from proofpoint1.mail.rice.edu ([128.42.201.100] helo=pp1.rice.edu) by makus.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1WLvMK-0001yi-Cn for pgsql-hackers@postgresql.org; Fri, 07 Mar 2014 14:02:46 +0000 Received: from pps.filterd (pp1.rice.edu [127.0.0.1]) by pp1.rice.edu (8.14.5/8.14.5) with SMTP id s27E1YrD008790; Fri, 7 Mar 2014 08:02:41 -0600 Received: from mh3.mail.rice.edu (mh3.mail.rice.edu [128.42.199.10]) by pp1.rice.edu with ESMTP id 1jexny8b3t-1; Fri, 07 Mar 2014 08:02:41 -0600 X-Virus-Scanned: by amavis-2.7.0 at mh3.mail.rice.edu, auth channel X-SMTP-Auth: no X-SMTP-Auth: no X-SMTP-Auth: no X-SMTP-Auth: no X-SMTP-Auth: no X-SMTP-Auth: no Received: from aart.rice.edu (aart.rice.edu [168.7.56.48]) by mh3.mail.rice.edu (Postfix) with ESMTP id 1D2F040194; Fri, 7 Mar 2014 08:02:41 -0600 (CST) Received: by aart.rice.edu (Postfix, from userid 18612) id 126F210026C; Fri, 7 Mar 2014 08:02:41 -0600 (CST) Date: Fri, 7 Mar 2014 08:02:41 -0600 From: "ktm@rice.edu" To: Robert Haas Cc: Jeff Janes , Heikki Linnakangas , Greg Stark , Tan Tran , PostgreSQL-development Subject: Re: GSoC on WAL-logging hash indexes Message-ID: <20140307140241.GO1150@aart.rice.edu> References: <54977A8C-4AF5-4BCC-B021-78E9CA978077@gmail.com> <531873E8.6050802@vmware.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.20 (2009-12-10) X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 kscore.is_bulkscore=7.21644966006352e-15 kscore.compositescore=0 circleOfTrustscore=0 compositescore=0.995703810101747 urlsuspect_oldscore=0.995703810101747 suspectscore=0 recipient_domain_to_sender_totalscore=0 phishscore=0 bulkscore=0 kscore.is_spamscore=0 recipient_to_sender_totalscore=0 recipient_domain_to_sender_domain_totalscore=19 rbsscore=0.995703810101747 spamscore=0 recipient_to_sender_domain_totalscore=0 urlsuspectscore=0.9 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=7.0.1-1305240000 definitions=main-1403070049 X-Pg-Spam-Score: -1.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 Thu, Mar 06, 2014 at 06:14:21PM -0500, Robert Haas wrote: > On Thu, Mar 6, 2014 at 3:44 PM, Jeff Janes wrote: > > > > I've been tempted to implement a new type of hash index that allows both WAL > > and high concurrency, simply by disallowing bucket splits. At the index > > creation time you use a storage parameter to specify the number of buckets, > > and that is that. If you mis-planned, build a new index with more buckets, > > possibly concurrently, and drop the too-small one. > > Yeah, we could certainly do something like that. It sort of sucks, > though. I mean, it's probably pretty easy to know that starting with > the default 2 buckets is not going to be enough; most people will at > least be smart enough to start with, say, 1024. But are you going to > know whether you need 32768 or 1048576 or 33554432? A lot of people > won't, and we have more than enough reasons for performance to degrade > over time as it is. > It would be useful to have a storage parameter for the target size of the index, even if it is not exact, to use in the initial index build to avoid the flurry of i/o caused by bucket splits as the index grows. Regards, Ken -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers