OpenFTS vs Tsearch2 comment

diff --git a/contrib/tsearch2/README.tsearch2 b/contrib/tsearch2/README.tsearch2
index 801e3fe5f6bda6fab4c210e6ab0eecad93c3b542..e01807306e7d28b0955a1b476b324d5962403afd 100644 (file)
--- 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