From: | Zeugswetter Andreas SB <ZeugswetterA(at)wien(dot)spardat(dot)at> |
---|---|
To: | "'Oleg Bartunov'" <oleg(at)sai(dot)msu(dot)su>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | AW: Re: GiST for 7.1 !! |
Date: | 2001-01-11 10:25:25 |
Message-ID: | 11C1E6749A55D411A9670001FA6879633681A6@sdexcsrv1.f000.d0188.sd.spardat.at |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
> > > we've almost totally rewrite gist.c because old code and algorithm
> > > were not suitable for variable size keys. I think it might be
> > > submitted into 7.1 beta source tree.
> >
> > Urgh. Dropping in a total rewrite when we're already past
> beta3 doesn't
> > strike me as good project management practice --- especially if the
> > rewrite was done to add features (ie variable-size keys) not merely
> > fix bugs. I think it might be more prudent to hold this for 7.2.
>
> OK. If our changes will not go to 7.1, is't possible to create
> feature archive and announce it somewhere. It would be nice if
> people could test it. Anyway, I'll create web page with all
> docs and patches. I'm afraid one more year to 7.2 is enough for
> GiST to die :-)
I think featureism is the the most prominent argument for PostgreSQL.
Thus standing before a decision to eighter fix GiST bugs and risc a new
bug (limited to GiST) because of an added feature or shipping a known
broken GiST, my vote would definitely be to add Oleg's patch.
Andreas
From | Date | Subject | |
---|---|---|---|
Next Message | Oleg Bartunov | 2001-01-11 10:54:06 | Re: AW: Re: GiST for 7.1 !! |
Previous Message | Oleg Bartunov | 2001-01-11 10:09:19 | Re: Re: GiST for 7.1 !! |