Received: from maia.hub.org (maia-2.hub.org [200.46.204.251]) by mail.postgresql.org (Postfix) with ESMTP id D3E021337B9C for ; Sat, 12 Feb 2011 14:21:34 -0400 (AST) Received: from mail.postgresql.org ([200.46.204.86]) by maia.hub.org (mx1.hub.org [200.46.204.251]) (amavisd-maia, port 10024) with ESMTP id 50581-04 for ; Sat, 12 Feb 2011 18:21:27 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from mail-gx0-f174.google.com (mail-gx0-f174.google.com [209.85.161.174]) by mail.postgresql.org (Postfix) with ESMTP id E25321337B98 for ; Sat, 12 Feb 2011 14:21:26 -0400 (AST) Received: by gxk9 with SMTP id 9so1526967gxk.19 for ; Sat, 12 Feb 2011 10:21:25 -0800 (PST) Received: by 10.151.98.5 with SMTP id a5mr2246750ybm.327.1297534432570; Sat, 12 Feb 2011 10:13:52 -0800 (PST) Received: from [192.168.1.100] (c-76-102-27-65.hsd1.ca.comcast.net [76.102.27.65]) by mx.google.com with ESMTPS id p2sm409020ybh.15.2011.02.12.10.13.50 (version=SSLv3 cipher=OTHER); Sat, 12 Feb 2011 10:13:51 -0800 (PST) Subject: Re: btree_gist (was: CommitFest progress - or lack thereof) From: Jeff Davis To: Oleg Bartunov Cc: Stephen Frost , Robert Haas , pgsql-hackers@postgresql.org In-Reply-To: References: <20110211213738.GY4116@tamriel.snowman.net> <20110212124716.GB4116@tamriel.snowman.net> Content-Type: text/plain; charset="UTF-8" Date: Sat, 12 Feb 2011 10:13:50 -0800 Message-ID: <1297534430.27157.672.camel@jdavis> Mime-Version: 1.0 X-Mailer: Evolution 2.30.3 Content-Transfer-Encoding: 7bit X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=-2.6 tagged_above=-5 required=5 tests=BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7 X-Spam-Level: X-Archive-Number: 201102/1165 X-Sequence-Number: 181954 On Sat, 2011-02-12 at 18:53 +0300, Oleg Bartunov wrote: > > It sure seems like > > http://www.postgresql.org/docs/9.0/static/btree-gist.html could be and > > should be improved, in general.. If this module is really still just a > > test bed for GiST, then perhaps it's not a big deal.. > > No, it's quite useful and used in many projects, since it's the only way > to create multicolumn gist indexes like (tsvector,date). +1 btree_gist is essentially required for exclusion constraints to be useful in a practical way. In fact, can you submit it for the next commitfest to be included in core? That would allow range types and exclusion constraints to be used out-of-the-box in 9.2. Only if you think it's reasonable to put it in core, of course. If extensions are easy enough to install, maybe that's not really necessary. Regards, Jeff Davis