# 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 juni 2016 om 02:19 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:** 9

<div class="post-metadata">

**Author:** ![Mittineague](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/mittineague/32/114259_2.png) [@Mittineague](https://meta.discourse.org/u/Mittineague)\
**Post date:** [28 juni 2016 om 07:34 UTC](https://meta.discourse.org/t/no-search-results-are-shown-for-stopwords/46541/9 "2016-06-28T07:34:03Z")

</div>

> [@mpalmer](#):
>
> learning a lot more about full-text search and PostgreSQL internals than you ever cared to know. It’s certainly not something that would ever be a “standard” feature, because it’s so incredibly niche. You’d be better off creating some sort of custom index plugin that kept a mapping of all the words and their associated topic IDs

There sure is a lot more to it than I ever imagined.

The custom index could be doable. AFAIK there are 127 stops. A bit, but not overwhelmingly so.

[https://apt-browse.org/browse/ubuntu/trusty/main/i386/postgresql-9.3/9.3.4-1/file/usr/share/postgresql/9.3/tsearch\_data/english.stop](https://apt-browse.org/browse/ubuntu/trusty/main/i386/postgresql-9.3/9.3.4-1/file/usr/share/postgresql/9.3/tsearch_data/english.stop)

---

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