From 92107522ed3568740ec7c3597db50b5c3a6e84d3 Mon Sep 17 00:00:00 2001 From: Christophe Pettus Date: Mon, 30 May 2016 09:40:44 -0700 Subject: [PATCH] Fixed #26684 -- Removed incorrect index example in docs/ref/contrib/postgres/search.txt. --- docs/ref/contrib/postgres/search.txt | 11 +++-------- 1 file 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 +`_. ``SearchVectorField`` ---------------------