Glad to hear GiST in 7.2 isn't broken :-)
We miss the topic, what was the problem ?
Do we need to fix GiST code for 7.3 ?
proposal for null-safe GiST interface is available
http://fts.postgresql.org/db/mw/msg.html?mid=1028327
and discussion
http://fts.postgresql.org/db/mw/msg.html?mid=1025848
Regards, Oleg
On Wed, 29 May 2002, Tom Lane wrote:
> >> Urgh ... that means GiST indexing is actually broken, because GiST
> >> currently handles multicolumns but not nulls.
>
> Actually, it appears that 7.2 GiST does handle NULLs in columns after
> the first one, which I think is enough to avoid the problem Jan
> mentioned. The boolean column pg_am.amindexnulls is not really
> sufficient to describe this behavior accurately. Looking at current
> uses it seems correct to leave it set FALSE for GiST.
>
> In short: false alarm; the 7.2 code is okay as-is, at least on this
> particular point.
>
> regards, tom lane
>
> ---------------------------(end of broadcast)---------------------------
> TIP 2: you can get off all lists at once with the unregister command
> (send "unregister YourEmailAddressHere" to majordomo@postgresql.org)
>
Regards, Oleg
_____________________________________________________________
Oleg Bartunov, sci.researcher, hostmaster of AstroNet,
Sternberg Astronomical Institute, Moscow University (Russia)
Internet: oleg@sai.msu.su, http://www.sai.msu.su/~megera/
phone: +007(095)939-16-83, +007(095)939-23-83
