Why not keeping positions in GIN? - Mailing list pgsql-hackers

From Hitoshi Harada
Subject Why not keeping positions in GIN?
Date
Msg-id 00f701c79e8b$23d31fb0$5f01a8c0@daraha
Whole thread Raw
Responses Re: Why not keeping positions in GIN?  ("Guillaume Smet" <guillaume.smet@gmail.com>)
Re: Why not keeping positions in GIN?  (Oleg Bartunov <oleg@sai.msu.su>)
List pgsql-hackers
Hi, 

I was walking through GIN am source code these days, and found that it has
only posting lists but no positions related those.

The reason I was doing that is, to try to implement n-gram text search index
on GIN for myself. As you know Japanese is not like English or other
European languages. If you write Japanese (or other 'not separated') text
index by n-gram, it should have entry positions on the entry as well as the
posting lists, because you must know if each split query key are joined with
each other in the data. To know this, position must be there.

It's not only about Japanese. When you search "phrase" for text in English,
the same logic above will be needed. I don't research about tsearch2 but is
there any problem?? Also, in some case int-array inverted index needs the
entry positions as well, I guess. Obtaining positions with posting lists is
"general" enough for GIN, isn't it?

Is there any future plan around it? 


Regards, 

Hitoshi Harada




pgsql-hackers by date:

Previous
From: Andrew Dunstan
Date:
Subject: Re: like/ilike improvements
Next
From: mark@mark.mielke.cc
Date:
Subject: Re: like/ilike improvements