OpenFTS vs Tsearch2 comment
This commit is contained in:
parent
d702313f0d
commit
8753157739
|
@ -32,6 +32,17 @@ Tsearch2 - full text search extension for PostgreSQL
|
||||||
|
|
||||||
See [11]Documentation Roadmap for links to documentation.
|
See [11]Documentation Roadmap for links to documentation.
|
||||||
|
|
||||||
|
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.
|
||||||
|
|
||||||
Authors
|
Authors
|
||||||
|
|
||||||
* Oleg Bartunov <oleg@sai.msu.su>, Moscow, Moscow University, Russia
|
* Oleg Bartunov <oleg@sai.msu.su>, Moscow, Moscow University, Russia
|
||||||
|
|
Loading…
Reference in New Issue