# No search results are shown for stopwords

**URL:** <https://meta.discourse.org/t/no-search-results-are-shown-for-stopwords/46541>\
**Category:** Product Support\
**Created:** [28 ביוני,‏ 2016,‏ 2:19am UTC](https://meta.discourse.org/t/no-search-results-are-shown-for-stopwords/46541 "2016-06-28T02:19:43Z")\
**Posts on this page:** 1\
**Showing post:** 10

<div class="post-metadata">

**Author:** ![mpalmer](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/mpalmer/32/45740_2.png) [@mpalmer](https://meta.discourse.org/u/mpalmer)\
**Post date:** [28 ביוני,‏ 2016,‏ 9:37am UTC](https://meta.discourse.org/t/no-search-results-are-shown-for-stopwords/46541/10 "2016-06-28T09:37:40Z")

</div>

The trick, if you want to use a different stop word list (or not have any at all) is to define a custom dictionary and language profile (or whatever PostgreSQL calls it) that doesn’t have the stop words in it, and then reconfigure your full-text indexing to use that instead of the standard English one. I’ve done it once, a long long time ago, and I have no interest in repeating the experience.

---

_[View the full topic](https://meta.discourse.org/t/no-search-results-are-shown-for-stopwords/46541)._
