|From:||Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>|
|To:||Robert Haas <robertmhaas(at)gmail(dot)com>|
|Cc:||Oleg Bartunov <oleg(at)sai(dot)msu(dot)su>, Teodor Sigaev <teodor(at)sigaev(dot)ru>, pgsql-hackers(at)postgresql(dot)org|
|Subject:||Re: btree_gist (was: CommitFest progress - or lack thereof)|
|Views:||Raw Message | Whole Thread | Download mbox|
Robert Haas <robertmhaas(at)gmail(dot)com> writes:
> 2011/2/17 Oleg Bartunov <oleg(at)sai(dot)msu(dot)su>:
>> We need to fix inet support as Tom complained and then will commit.
> I think those are two separate issues.
Yeah ... also, fixing the inet problem looked to me like it'd probably
be a major compatibility break (change in on-disk index contents).
Not something to rush into at the end of a development cycle.
In any case, I was pointing to that as a reason that btree_gist wasn't
ready to be in core. It has nothing to do with KNN-ifying the module.
I would like to see that happen before 9.1, else KNN will go out with
not very many actual use-cases supported.
regards, tom lane
|Next Message||Bruce Momjian||2011-02-17 15:22:30||Re: Debian readline/libedit breakage|
|Previous Message||Tom Lane||2011-02-17 15:09:37||Re: Re: [COMMITTERS] pgsql: Fix blatantly uninitialized variable in recent commit.|
|Next Message||Tom Lane||2011-02-17 21:43:12||Re: btree_gist (was: CommitFest progress - or lack thereof)|
|Previous Message||Robert Haas||2011-02-17 11:34:25||Re: btree_gist (was: CommitFest progress - or lack thereof)|