diff options
| author | Christophe Pettus <cpettus@pgexperts.com> | 2016-05-30 09:40:44 -0700 |
|---|---|---|
| committer | Tim Graham <timograham@gmail.com> | 2016-05-30 14:21:05 -0400 |
| commit | 92107522ed3568740ec7c3597db50b5c3a6e84d3 (patch) | |
| tree | c59ada620e04f1d73c85c8f11240e1e050cef22f /docs/ref | |
| parent | f1e408ff40d2c1753f92515c70a44634b4d47467 (diff) | |
Fixed #26684 -- Removed incorrect index example in docs/ref/contrib/postgres/search.txt.
Diffstat (limited to 'docs/ref')
| -rw-r--r-- | docs/ref/contrib/postgres/search.txt | 11 |
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`` --------------------- |