| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Jeff Davis <pgsql(at)j-davis(dot)com> |
| Cc: | Oleg Bartunov <oleg(at)sai(dot)msu(dot)su>, 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 21:45:16 |
| Message-ID: | 24431.1297547116@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-rrreviewers |
Jeff Davis <pgsql(at)j-davis(dot)com> writes:
> 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.
btree_gist is entirely unready to be included in core.
http://archives.postgresql.org/pgsql-bugs/2010-10/msg00104.php
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dimitri Fontaine | 2011-02-12 21:46:30 | Re: Debian readline/libedit breakage |
| Previous Message | Kevin Grittner | 2011-02-12 21:42:17 | Re: SQL/MED - file_fdw |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Oleg Bartunov | 2011-02-12 21:50:24 | Re: btree_gist (was: CommitFest progress - or lack thereof) |
| Previous Message | Jeff Davis | 2011-02-12 18:13:50 | Re: btree_gist (was: CommitFest progress - or lack thereof) |