From: | Jeff Davis <pgsql(at)j-davis(dot)com> |
---|---|
To: | Oleg Bartunov <oleg(at)sai(dot)msu(dot)su> |
Cc: | Stephen Frost <sfrost(at)snowman(dot)net>, Robert Haas <robertmhaas(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: btree_gist (was: CommitFest progress - or lack thereof) |
Date: | 2011-02-12 18:13:50 |
Message-ID: | 1297534430.27157.672.camel@jdavis |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-rrreviewers |
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
From | Date | Subject | |
---|---|---|---|
Next Message | Pavel Stehule | 2011-02-12 18:58:06 | Re: Sorting. When? |
Previous Message | Kevin Grittner | 2011-02-12 17:53:57 | Re: SSI bug? |
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2011-02-12 21:45:16 | Re: btree_gist (was: CommitFest progress - or lack thereof) |
Previous Message | Oleg Bartunov | 2011-02-12 15:53:33 | Re: btree_gist (was: CommitFest progress - or lack thereof) |