#33459: Explain how to optimize full text search with SearchVectorField and
GinIndex
--------------------------------------+------------------------------------
Reporter: Thomas Aglassinger | Owner: nobody
Type: Cleanup/optimization | Status: new
Component: Documentation | Version: 4.0
Severity: Normal | Resolution:
Keywords: postgres | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 1
Easy pickings: 0 | UI/UX: 0
--------------------------------------+------------------------------------
Comment (by Thomas Aglassinger):
Replying to [comment:8 Mariusz Felisiak]:
> In the
[https://docs.djangoproject.com/en/dev/ref/contrib/postgres/search/#performance
Performance] section we're talking about ''"**a functional index** which
matches the search vector you wish to use"'' so rather
> {{{
> GinIndex(SearchVector('body_text'), name='body_search_vector_idx')
> }}}
> What do you think about adding?
Agreed, this would be a good example for the performance section.
We still don't have an example for the `SearchVectorField` though but I
guess people have to live with that for the time being.
> Would you like to prepare a patch? (if you like it of course)
If it saves you work, I can do that. I can't really take credits for the
contents though as they are too different to my proposal. I also would
make a new PR to avoid clutter in the repository log.
Let me know if I should.
--
Ticket URL: <https://code.djangoproject.com/ticket/33459#comment:10>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/067.294de8968decdb1b9b1ef0680dfcef16%40djangoproject.com.
