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

Re: [PATCHES] Include Lists for Text Search

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Teodor Sigaev <teodor(at)sigaev(dot)ru>
Cc: Oleg Bartunov <oleg(at)sai(dot)msu(dot)su>, Simon Riggs <simon(at)2ndquadrant(dot)com>, pgsql-hackers(at)postgresql(dot)org, pgsql-patches(at)postgresql(dot)org
Subject: Re: [PATCHES] Include Lists for Text Search
Date: 2008-03-10 15:10:55
Message-ID: 24143.1205161855@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-hackerspgsql-patches
Teodor Sigaev <teodor(at)sigaev(dot)ru> writes:
>> Hmm, I can see how some middleware would help with folding or not
>> folding the input token, but what about the words coming from the
>> dictionary file (particularly the *output* lexeme)?  It's not apparent
>> to me that it's sensible to try to control that from outside the
>> dictionary.

> Right now I see an significant advantage of such layer: two possible extension 
> of dictionary  (filtering and storing original form) are independent from nature 
> of dictionary. So, instead of modifying of every dictionary we can add some 
> layer, common for all dictionary. With syntax like:

> CREATE/ALTER TEXT SEARCH DICTIONARY foo  (...) WITH ( filtering=on|off, 
> store_original=on|off );

> Or per token's type/dictionary pair.

Well, if you think this can/should be done somewhere outside the
dictionary, should I revert the applied patch?

			regards, tom lane

In response to

Responses

pgsql-hackers by date

Next:From: Teodor SigaevDate: 2008-03-10 15:21:03
Subject: Re: [PATCHES] Include Lists for Text Search
Previous:From: Teodor SigaevDate: 2008-03-10 14:59:27
Subject: Re: Include Lists for Text Search

pgsql-patches by date

Next:From: Tom LaneDate: 2008-03-10 15:20:40
Subject: Re: Very slow (2 tuples/second) sequential scan after bulk insert; speed returns to ~500 tuples/second after commit
Previous:From: Craig RingerDate: 2008-03-10 15:10:00
Subject: Re: Very slow (2 tuples/second) sequential scan after bulk insert; speed returns to ~500 tuples/second after commit

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