summaryrefslogtreecommitdiff
path: root/docs/ref
diff options
context:
space:
mode:
Diffstat (limited to 'docs/ref')
-rw-r--r--docs/ref/contrib/postgres/search.txt11
1 files changed, 3 insertions, 8 deletions
diff --git a/docs/ref/contrib/postgres/search.txt b/docs/ref/contrib/postgres/search.txt
index 24000d341b..533c3ec504 100644
--- a/docs/ref/contrib/postgres/search.txt
+++ b/docs/ref/contrib/postgres/search.txt
@@ -165,14 +165,9 @@ than comparing the size of an integer, for example.
In the event that all the fields you're querying on are contained within one
particular model, you can create a functional index which matches the search
-vector you wish to use. For example:
-
-.. code-block:: sql
-
- CREATE INDEX body_text_search ON blog_entry (to_tsvector(body_text));
-
-This index will then be used by subsequent queries. In many cases this will be
-sufficient.
+vector you wish to use. The PostgreSQL documentation has details on
+`creating indexes for full text search
+<http://www.postgresql.org/docs/current/static/textsearch-tables.html#TEXTSEARCH-TABLES-INDEX>`_.
``SearchVectorField``
---------------------