Re: Term positions in GIN fulltext index

From: Alexander Korotkov <aekorotkov(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Yoann Moreau <yoann(dot)moreau(at)univ-avignon(dot)fr>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Term positions in GIN fulltext index
Date: 2011-11-03 19:40:13
Message-ID: CAPpHfdtVWHJR3C5WKYHPxBajT5mtmGPKbdOQGrhxGTcACeNZ-A@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, Nov 3, 2011 at 11:01 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:

> Yoann Moreau <yoann(dot)moreau(at)univ-avignon(dot)fr> writes:
> > I'm using a GIN index for a text column on a big table. I use it to rank
> > the rows, but I also need to get the term positions for each document of
> a
> > subset of documents for one or more terms. I suppose these positions are
> stored
> > in the index as the to_tsvector shows them : 'lexeme':{positions}
>
> I'm pretty sure that a GIN index on tsvector does *not* store positions
> --- it only knows about the strings. Don't know one way or the other
> about GIST.
>
GiST index doesn't store positions too. See gtsvector_compress. It converts
tsvector to array of crc32 of words. If that value is anyway too large then
function converts it to signature.

------
With best regards,
Alexander Korotkov.

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Kevin Grittner 2011-11-03 19:45:50 Re: warning in pg_upgrade
Previous Message Marcin Mańk 2011-11-03 19:34:15 Re: Term positions in GIN fulltext index