Video yükleniyor...

Video Yüklenemedi

Ana Sayfaya Dön

Inverted indexes are the perfect structure for text search. "Inverted" here doesn't mean upside-down. Rather that it's an inversion of the original data. We take every distinct word from a set of documents and build a "posting list" of references back to every location where that word is used....

32,297 görüntüleme • 18 gün önce •via X (Twitter)

10 Yorum

Eddy profil fotoğrafı
Eddy18 gün önce

FAST balls indeed

Rishabh Chauhan profil fotoğrafı
Rishabh Chauhan18 gün önce

will you open source it?

Ratul Dawar profil fotoğrafı
Ratul Dawar18 gün önce

But this doesn’t include like queries right?

Ben Dicken profil fotoğrafı
Ben Dicken18 gün önce

The index is the structure for making searches fast. TIN has a complete syntax for specifying search queries, TINQL

Samantha profil fotoğrafı
Samantha18 gün önce

Hi Ben, just following up on the DM I just sent regarding a potential Bloomberg interview. Would love to hear from you when you get a chance.

shane borden 🛩️ profil fotoğrafı
shane borden 🛩️18 gün önce

How did you resolve the hot block 0 issue with regular GiN indexes. No more pending list? Fast update?

Darius Rey profil fotoğrafı
Darius Rey18 gün önce

I Use it too I how I can Filter/orga my data in the cash (Looked by superbuffer)

Wanten profil fotoğrafı
Wanten17 gün önce

@grok 这个索引方式支持多字符串词组吗?

liprais profil fotoğrafı
liprais18 gün önce

good idea,now try with chinese texts

Pankaj Kumar profil fotoğrafı
Pankaj Kumar18 gün önce

Half the teams I see bolt on Elasticsearch before they have 10k rows. Postgres was fine, Ben.

Benzer Videolar

Big moment for Postgres! AI coding tools have been surprisingly bad at writing Postgres code. Not because the models are dumb, but because of how they learned SQL in the first place. LLMs are trained on the internet, which is full of outdated Stack Overflow answers and quick-fix tutorials. So when you ask an AI to generate a schema, it gives you something that technically runs but misses decades of Postgres evolution, like: - No GENERATED ALWAYS AS IDENTITY (added in PG10) - No expression or partial indexes - No NULLS NOT DISTINCT (PG15) - Missing CHECK constraints and proper foreign keys - Generic naming that tells you nothing But this is actually a solvable problem. You can teach AI tools to write better Postgres by giving them access to the right documentation at inference time. This exact solution is actually implemented in the newly released pg-aiguide by Tiger Data - Creators of TimescaleDB, which is an open-source MCP server that provides coding tools access to 35 years of Postgres expertise. In a gist, the MCP server enables: - Semantic search over the official PostgreSQL manual (version-aware, so it knows PG14 vs PG17 differences) - Curated skills with opinionated best practices for schema design, indexing, and constraints. I ran an experiment with Claude Code to see how well this works, and worked with the team to put this together. Prompt: "Generate a schema for an e-commerce site twice, one with the MCP server disabled, one with it enabled. Finally, run an assessment to compare the generated schemas." The run with the MCP server led to: - 420% more indexes (including partial and expression indexes) - 235% more constraints - 60% more tables (proper normalization) - 11 automation functions and triggers - Modern PG17 patterns throughout The MCP-assisted schema had proper data integrity, performance optimizations baked in, and followed naming conventions that actually make sense in production. pg-aiguide works with Claude Code, Cursor, VS Code, and any MCP-compatible tool. It's free and fully open source. I have shared the repo in the replies!

Avi Chawla

187,280 görüntüleme • 9 ay önce