Re: Tsearch2 or openFTS ?
| От | Teodor Sigaev |
|---|---|
| Тема | Re: Tsearch2 or openFTS ? |
| Дата | |
| Msg-id | 3F311669.1070709@sigaev.ru обсуждение исходный текст |
| Ответ на | Tsearch2 or openFTS ? (psql-mail@freeuk.com) |
| Список | pgsql-general |
OpenFTS vs Tsearch2
OpenFTS is a middleware between application and database, so it uses
tsearch2 as a storage, while database engine is used as a query executor
(searching). Everything else (parsing of documents, query processing,
linguistics) carry outs on client side. That's why OpenFTS has its own
configuration table (fts_conf) and works with its own set of dictionaries.
OpenFTS is more flexible, because it could be used in multi-server
architecture with separated machines for repository of documents
(documents could be stored in file system), database and query engine.
psql-mail@freeuk.com wrote:
> While I continue trying to get tsearch2 up and running...
>
> When should a db designer opt for tsearch2 directly and when should
> they opt for openFTS?
>
--
Teodor Sigaev E-mail: teodor@sigaev.ru
В списке pgsql-general по дате отправления: