diff options
| author | Teodor Sigaev <teodor@sigaev.ru> | 2003-08-06 14:53:01 +0000 |
|---|---|---|
| committer | Teodor Sigaev <teodor@sigaev.ru> | 2003-08-06 14:53:01 +0000 |
| commit | 87531577391f769963fab657c6698d3b79dd87d0 (patch) | |
| tree | 8e7eeebd87226a34388ad949210881cf2dc07734 | |
| parent | d702313f0d7b811484d05e495a2353b211475b5e (diff) | |
| download | postgresql-87531577391f769963fab657c6698d3b79dd87d0.tar.gz postgresql-87531577391f769963fab657c6698d3b79dd87d0.zip | |
OpenFTS vs Tsearch2 comment
| -rw-r--r-- | contrib/tsearch2/README.tsearch2 | 13 |
1 files changed, 12 insertions, 1 deletions
diff --git a/contrib/tsearch2/README.tsearch2 b/contrib/tsearch2/README.tsearch2 index 801e3fe5f6b..e01807306e7 100644 --- a/contrib/tsearch2/README.tsearch2 +++ b/contrib/tsearch2/README.tsearch2 @@ -31,7 +31,18 @@ Tsearch2 - full text search extension for PostgreSQL * specify the parser used to process a document. 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 * Oleg Bartunov <oleg@sai.msu.su>, Moscow, Moscow University, Russia |