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

Re: [GENERAL] Fragments in tsearch2 headline

From: "Pierre-Yves Strub" <pierre(dot)yves(dot)strub(at)gmail(dot)com>
To: sushant354(at)gmail(dot)com
Cc: "Teodor Sigaev" <teodor(at)sigaev(dot)ru>, "Pgsql Hackers" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: [GENERAL] Fragments in tsearch2 headline
Date: 2008-05-25 00:20:05
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-generalpgsql-hackers
On Sat, May 24, 2008 at 11:18 PM, Sushant Sinha <sushant354(at)gmail(dot)com> wrote:

> Does this mean we want a unified function ts_headline and we trigger the
> fragments if NumFragments is specified? It seems that introducing a new
> function which can take configuration OID, or name is complex as there
> are so many functions handling these issues in wparser.c.
> If this is true then we need to just  add marking of headline words in
> prsd_headline. Otherwise we will need another prsd_headline_with_covers
> function.

I think that we could merge down the two functions using a default
cover of the whole text when NumCovers if missing. I started writing
the function. The only missing information is, as you stated, the
missing posititions in HeadlineParsedText.

In response to

pgsql-hackers by date

Next:From: Tom LaneDate: 2008-05-25 03:15:27
Subject: Re: \df displaying volatility
Previous:From: Rainer BauerDate: 2008-05-24 22:01:10
Subject: Re: Execution-time-sensitive timestamp regression tests

pgsql-general by date

Next:From: jcvlzDate: 2008-05-25 02:41:43
Subject: Re: best er modeling tool for postgreSQL
Previous:From: Steve AtkinsDate: 2008-05-24 21:59:04
Subject: Re: Optimzing Postgresql

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