From 87531577391f769963fab657c6698d3b79dd87d0 Mon Sep 17 00:00:00 2001 From: Teodor Sigaev Date: Wed, 6 Aug 2003 14:53:01 +0000 Subject: [PATCH] OpenFTS vs Tsearch2 comment --- contrib/tsearch2/README.tsearch2 | 13 ++++++++++++- 1 file changed, 12 insertions(+), 1 deletion(-) diff --git a/contrib/tsearch2/README.tsearch2 b/contrib/tsearch2/README.tsearch2 index 801e3fe5f6..e01807306e 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 , Moscow, Moscow University, Russia -- GitLab