| From: | Simon Riggs <simon(at)2ndquadrant(dot)com> |
|---|---|
| To: | Teodor Sigaev <teodor(at)sigaev(dot)ru> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Include Lists for Text Search |
| Date: | 2007-09-10 13:49:42 |
| Message-ID: | 1189432182.4281.252.camel@ebony.site |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-patches |
On Mon, 2007-09-10 at 16:48 +0400, Teodor Sigaev wrote:
> > There are clear indications that indexing too many words is a problem
> > for both GIN and GIST. If people already know what they'll be looking
GIN is great, sorry if that sounded negative.
> GIN doesn't depend strongly on number of words. It has log(N) behaviour for
> numbers of words because of using B-Tree over words.
log(N) in the number of distinct words, but every word you index results
in an index insert, so if we index more words than we need then the
insert rate will go down.
--
Simon Riggs
2ndQuadrant http://www.2ndQuadrant.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrew Dunstan | 2007-09-10 13:51:09 | Re: invalidly encoded strings |
| Previous Message | Simon Riggs | 2007-09-10 13:27:59 | Re: Include Lists for Text Search |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrew Dunstan | 2007-09-10 13:51:09 | Re: invalidly encoded strings |
| Previous Message | Simon Riggs | 2007-09-10 13:27:59 | Re: Include Lists for Text Search |