Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

Commit8753157

Browse files
committed
OpenFTS vs Tsearch2 comment
1 parentd702313 commit8753157

File tree

1 file changed

+12
-1
lines changed

1 file changed

+12
-1
lines changed

‎contrib/tsearch2/README.tsearch2

Lines changed: 12 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -31,7 +31,18 @@ Tsearch2 - full text search extension for PostgreSQL
3131
* specify the parser used to process a document.
3232

3333
See [11]Documentation Roadmap for links to documentation.
34-
34+
35+
OpenFTS vs Tsearch2
36+
37+
OpenFTS is a middleware between application and database, so it uses
38+
tsearch2 as a storage, while database engine is used as a query executor
39+
(searching). Everything else (parsing of documents, query processing,
40+
linguistics) carry outs on client side. That's why OpenFTS has its own
41+
configuration table (fts_conf) and works with its own set of dictionaries.
42+
OpenFTS is more flexible, because it could be used in multi-server
43+
architecture with separated machines for repository of documents
44+
(documents could be stored in file system), database and query engine.
45+
3546
Authors
3647

3748
* Oleg Bartunov <oleg@sai.msu.su>, Moscow, Moscow University, Russia

0 commit comments

Comments
 (0)

[8]ページ先頭

©2009-2025 Movatter.jp