
Tin: full-text search for Postgres
Introducing TIN: full-text search for PostgresEric Ridge, Patrick Reynolds | September 16, 2026One of the Postgres features our customers ask us for the most is full-text search. Today, we are excited to announce TIN: a fast, full-featured, reliable full-text search extension for Postgres. TIN stands for "Text INdex," and that is what it does.TIN is available immediately as a GA release for all Postgres and Neki databases.
- ▪Introducing TIN: full-text search for PostgresEric Ridge, Patrick Reynolds | September 16, 2026One of the Postgres features our customers ask us for the most is full-text search.
- ▪Today, we are excited to announce TIN: a fast, full-featured, reliable full-text search extension for Postgres.
- ▪TIN stands for "Text INdex," and that is what it does.TIN is available immediately as a GA release for all Postgres and Neki databases.
Hacker News (Front Page) files mainly under programming. We currently carry 1,856 of its stories. Top-voted stories on Hacker News.
Story provenance
Source · retrieval · rights · ranking — open for full record
inspect →
Story provenance
Attribution is not the same as permission. This drawer separates discovery metadata, excerpts, WeSearch-generated summaries, reuse status, and whether the publisher receives the visit. Nothing here claims a legal grant the publisher has not made.
Record
| Original publisher | Planetscale |
| Canonical URL | https://planetscale.com/blog/introducing-tin |
| Publication time | Sat, 19 Sep 2026 13:52:06 +0000 |
| Retrieval time | 2026-09-19T14:18:46.600Z |
| Last seen | 2026-09-19T14:18:46.600Z |
| Headline source | Publisher (no WeSearch rewrite) |
| Excerpt source | publisher body |
| Excerpt method | First ~120 words (~800 chars) of extracted publisher body, fair-use limited. |
| Summary | WeSearch · cerebras-chat (WeSearch summarizer) |
| Summary source text | contentText |
| Citation coverage | Summary is a WeSearch-generated derivative; primary citation is the original publisher URL. |
| Cluster | r-z0l_CrPsh1 · 1 stories |
| Cluster logic | Grouped by semantic title/content similarity across sources within a rolling window. Same-publisher template collisions are excluded from coverage comparison. |
| Ranking reason | Story pages are not engagement-ranked. Hub feeds use recency, with optional source-diversified chronological ordering (cap consecutive stories per source). No personalized ranking. |
| Publisher visit | Yes — open original |
| Substitutes article? | No — link-out required for full text |
Rights status (four layers)
WeSearch handling by dimension
| Indexing | May the item be indexed (stored, ranked, made findable)? | Allowed |
| Snippet | May a short excerpt of the publisher's text be shown? | Allowed |
| AI summary | May WeSearch generate its own short summary of the article? | Limited |
| Retrieval / RAG | May the content be exposed for third-party retrieval-augmented generation? | Not asserted |
| Model training | May the content be used to train AI models? | Not asserted |
| Commercial reuse | May the content be reused commercially? | Not permitted |
Basis: Derived from the published RSS/Atom feed. Contact: [email protected]. Reviewed: 2026-07-24.
Opening excerpt (first ~120 words) tap to expand
Introducing TIN: full-text search for PostgresEric Ridge, Patrick Reynolds | September 16, 2026One of the Postgres features our customers ask us for the most is full-text search. Today, we are excited to announce TIN: a fast, full-featured, reliable full-text search extension for Postgres. TIN stands for "Text INdex," and that is what it does.TIN is available immediately as a GA release for all Postgres and Neki databases. Check it out:CREATE INDEX an_index_name ON table_name USING tin(text_column_name); SELECT * FROM table_name WHERE text_column_name ==> 'some words'; We built TIN because we believe a good text index should support:Boolean expressions, phrase queries, and span queriesFuzzy, wildcard, and regular-expression matching for termsCase and accent foldingCOUNT(*) queries and…
Excerpt limited to ~120 words for fair-use compliance. The full article is at Planetscale.