[4.0.x] Fixed #33459 -- Clarified index type in full text search docs.

Backport of 3a9b8b25d4 from main
This commit is contained in:
Thomas Aglassinger 2022-01-28 06:36:39 +01:00 committed by Mariusz Felisiak
parent 7c2d4d943b
commit 9a9c5b402b
1 changed files with 8 additions and 2 deletions

View File

@ -255,8 +255,14 @@ run into performance problems. Full text search is a more intensive process
than comparing the size of an integer, for example. than comparing the size of an integer, for example.
In the event that all the fields you're querying on are contained within one 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 particular model, you can create a functional
vector you wish to use. The PostgreSQL documentation has details on :class:`GIN <django.contrib.postgres.indexes.GinIndex>` or
:class:`GiST <django.contrib.postgres.indexes.GistIndex>` index which matches
the search vector you wish to use. For example::
GinIndex(SearchVector('body_text'), name='body_search_vector_idx')
The PostgreSQL documentation has details on
`creating indexes for full text search `creating indexes for full text search
<https://www.postgresql.org/docs/current/textsearch-tables.html#TEXTSEARCH-TABLES-INDEX>`_. <https://www.postgresql.org/docs/current/textsearch-tables.html#TEXTSEARCH-TABLES-INDEX>`_.