Tin: full-text search for Postgres
- ID
- 26483
- Status
- summarized
- Published
- 19 Sep 2026, 9:52 PM
- Fetched
- 21 Sep 2026, 8:53 PM
- Provider
- Hacker News
- Category
- dev-community
- Original URL
- https://planetscale.com/blog/introducing-tin
- Source URL
- https://hnrss.org/best
Summary
- Score
- 7.0
- Created
- 21 Sep 2026, 8:54 PM
- Tags
- Audience
- developersdatabase_learnerssaas_founders
What happened
PlanetScale released TIN (Text INdex), a GA full-text search extension for Postgres and their Neki sharded Postgres product. It supports boolean/phrase/span queries, fuzzy/wildcard/regex matching, BM25-ranked top-k, COUNT(*), and continuous updates with correct MVCC visibility—features the authors say no existing Postgres text index combined. Syntax is straightforward: CREATE INDEX ... USING tin(text_column) and query with WHERE col == 'search terms'.
Why it matters
If you currently run a separate Elasticsearch/Meilisearch/OpenSearch instance alongside Postgres just for full-text search, TIN may let you consolidate search into Postgres and drop that infrastructure—evaluate it against your actual query patterns (conjunction, phrase, fuzzy, BM25 ranking) before committing. This is a vendor product announcement with self-reported benchmarks, so test on your own data before migrating.
Discussion angle
Compare TIN against pg_trgm, tsvector/GIN, and Paradedb for real workloads—does consolidating search into Postgres actually save cost and complexity, or does it create a new operational dependency on PlanetScale's extension?