Skip Elasticsearch: Build Fast Full-Text Search Right in Supabase
Key topics
I wrote a short guide showing how to set it up and get blazing-fast search without extra infrastructure:
https://dev.to/reclusivecoder/skip-elasticsearch-build-blazing-fast-full-text-search-right-in-supabase-58pf
Would love to hear if others are using Postgres full-text search in production, and at what point/scale you'd rather switch to Elasticsearch.
The author suggests using Postgres full-text search in Supabase as a simpler alternative to Elasticsearch for small to medium apps, and seeks feedback from others who have used it in production.
Snapshot generated from the HN discussion
Discussion Activity
Light discussionFirst comment
2d
Peak period
1
48-51h
Avg / period
1
Key moments
- 01Story posted
Oct 3, 2025 at 1:53 AM EDT
3 months ago
Step 01 - 02First comment
Oct 5, 2025 at 4:43 AM EDT
2d after posting
Step 02 - 03Peak activity
1 comments in 48-51h
Hottest window of the conversation
Step 03 - 04Latest activity
Oct 5, 2025 at 4:43 AM EDT
3 months ago
Step 04
Generating AI Summary...
Analyzing up to 500 comments to identify key contributors and discussion patterns
Want the full context?
Jump to the original sources
Read the primary article or dive into the live Hacker News thread when you're ready.
Other projects claiming ElasticSearch API compatibility just don't work that good (e.g. zincsearch). Using plain lucene is also not that easy because the defaults are way less intuitive (e.g searching for terms with dashes, like click-bait).
Unfortunately DB fulltext indexes (mysql, SQL server, Oracle and PostgreSQL) tend to get HUGE over time and if there is anything you're trying to prevent it is filling the fast expensive database SSDs.
However, if you're just starting out, I'd recommend having a look at Meilisearch[1], with is way LEDs Resource hungry compared to elastic and offers similar features.
1: https://www.meilisearch.com