Re: [PERFORM] Partioning tsearch2 a table into chunks and accessing via views

On Aug 25, 2007, at 1:34 AM, Benjamin Arai wrote:

> There has to be another way to do incremental indexing without
> loosing that much performance.

This is the killer feature that prevents us from using the tsearch2
full text indexer on postgres.  we're investigating making a foreign
table from a SOLR full text index so our app only talks to Pg but the
text search is held in a good index.