Re: AW: Re: GiST for 7.1 !!

From: Hannu Krosing <hannu(at)tm(dot)ee>
To: Oleg Bartunov <oleg(at)sai(dot)msu(dot)su>
Cc: Zeugswetter Andreas SB <ZeugswetterA(at)wien(dot)spardat(dot)at>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, selkovjr(at)mcs(dot)anl(dot)gov, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: AW: Re: GiST for 7.1 !!
Date: 2001-01-11 16:06:41
Message-ID: 3A5DDA11.B976E4E3@tm.ee
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Oleg Bartunov wrote:
>
> On Thu, 11 Jan 2001, Zeugswetter Andreas SB wrote:
>
> > I think featureism is the the most prominent argument for PostgreSQL.

Exactly! Altough it has already lost much of it ;(

> > 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.

That's my vote too, specially if there will be some regression tests
accompanying the patches. The current (pre-patch) state of affairs with
GiST could probably be described as security-by-obscurity anyhow i.e.
"we have't tried it so we think it probably works" ;-)

Also I suspect there are still only a few users, most of them capable of
fixing inside gist.c if something nasti turns up.
They will be much more motivated to do so if it is in "official" sources
and not in the sources from postgresql-gist.org or somesuch ;)

> Definetely, our changes limited to GiST insert algorithm only.
> Other changes are bugfixes.

So applying _only_ bugfixes may also not be an option as they are not
well tested without the changed gist.c

-----------------
Hannu

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Hannu Krosing 2001-01-11 16:26:52 Re: Re: GiST for 7.1 !!
Previous Message Zeugswetter Andreas SB 2001-01-11 16:06:17 AW: AW: AW: Re: tinterval - operator problems on AIX