Skip site navigation (1) Skip section navigation (2)

Re: btree_gist (was: CommitFest progress - or lack thereof)

From: Oleg Bartunov <oleg(at)sai(dot)msu(dot)su>
To: Stephen Frost <sfrost(at)snowman(dot)net>
Cc: 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 15:53:33
Message-ID: Pine.LNX.4.64.1102121851050.278@sn.sai.msu.ru (view raw or flat)
Thread:
Lists: pgsql-hackerspgsql-rrreviewers
Stephen,

On Sat, 12 Feb 2011, Stephen Frost wrote:

> Oleg,
>
> * Oleg Bartunov (oleg(at)sai(dot)msu(dot)su) wrote:
>> what do you need for documentation ? From users point of view we add just
>> knn support and all examples are available in btree_gist.sql and sql
>> subdirectory. Contact me directly, if you have questions.
>
> It sure seems like
> http://www.postgresql.org/docs/9.0/static/btree-gist.html could be and
> should be improved, in general..  If this module is really still just a
> test bed for GiST, then perhaps it's not a big deal..

No, it's quite useful and used in many projects, since it's the only way
to create multicolumn gist indexes like (tsvector,date).


 	Regards,
 		Oleg
_____________________________________________________________
Oleg Bartunov, Research Scientist, Head of AstroNet (www.astronet.ru),
Sternberg Astronomical Institute, Moscow University, Russia
Internet: oleg(at)sai(dot)msu(dot)su, http://www.sai.msu.su/~megera/
phone: +007(495)939-16-83, +007(495)939-23-83

In response to

Responses

pgsql-hackers by date

Next:From: Tom LaneDate: 2011-02-12 16:14:23
Subject: Extensions vs PGXS' MODULE_PATHNAME handling
Previous:From: Stephen FrostDate: 2011-02-12 15:49:13
Subject: Re: Change pg_last_xlog_receive_location not to move backwards

pgsql-rrreviewers by date

Next:From: Jeff DavisDate: 2011-02-12 18:13:50
Subject: Re: btree_gist (was: CommitFest progress - or lack thereof)
Previous:From: Robert HaasDate: 2011-02-12 13:19:09
Subject: Re: btree_gist (was: CommitFest progress - or lack thereof)

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group