You Don't Need Elasticsearch
PostgreSQL Search for Developers Who'd Rather Not Manage Another Service
Start readingFull-text search is not a PostgreSQL extension. It is PostgreSQL.
The capability has been in your database this entire time. It simply never introduced itself.
Running a distributed cluster for a dataset that fits comfortably on a single server is not scaling. It is overengineering.
A search that requires exact spelling is not a search. It is a spelling test.
The most sophisticated architecture is the one that uses exactly what it needs and nothing more.
I confess I find something deeply reassuring about an algorithm that has outlasted every technology trend of the past century and shows no signs of retiring.
A recommendation that includes only benefits is not a recommendation. It is a sales pitch.
No one is asking you to leap. I am asking you to walk, at your own pace, with the ability to turn back at any point.
I would rather you know this now, from me, than discover it during implementation from a stack trace.
It has been my privilege to attend to you.
Table of Contents
Part I: The Argument
Part II: The Five Pillars of Search
Part III: Beyond Search
Part IV: Deployment and Scale
Part V: Framework Integration
Part VI: Gold Lapel and the Road Forward
Back Matter
What's Next — You Don't Need MongoDB Waiterisms — BonusCopyright © 2026 Gold Lapel. All rights reserved. First edition, 2026.