Skip to content
Why Database Indexing on JSON Fields Fails in Production episode artwork

Jun 21, 2026 8 min

Why Database Indexing on JSON Fields Fails in Production

from Database Tech with Fexingo: SQL, NoSQL, and Data Storage Conversations Hosted by Fexingo

Episode 64 of Database Tech with Fexingo dives into a trap that catches even senior engineers: indexing JSON fields in PostgreSQL and MySQL. Lucas and Luna dissect a real incident from a mid-size e-commerce company whose product search slowed to a crawl after they indexed a JSONB column with a GIN index. They explain why JSON indexes look great on paper but explode in size and cost under write-heavy workloads — and how the team fixed it with a generated column index instead. Expect concrete numbers: the index was 8x larger than equivalent columns, and query latency jumped from 12 milliseconds to over 2 seconds during peak traffic. If you're storing JSON in a relational database, this episode will save you from a painful Monday morning. #JSONIndexing #PostgreSQL #MySQL #GINIndex #GeneratedColumn #DatabasePerformance #IndexBloat #DatabaseEngineering #QueryOptimization #Ecommerce #ProductionIncident #DatabaseTuning #Technology #DatabaseTech #FexingoBusiness #BusinessPodcast #SQL #NoSQL Keep every episode free: buymeacoffee.com/fexingo

Episode details come from the podcast's RSS feed.

Embed this episode

Ready to play

Why Database Indexing on JSON Fields Fails in Production

0:00 8:20

No transcript yet.

Requests help us decide what to transcribe next.

Frequently asked questions

How long is this episode of Database Tech with Fexingo: SQL, NoSQL, and Data Storage Conversations?

This episode is 8 minutes long.

When was this Database Tech with Fexingo: SQL, NoSQL, and Data Storage Conversations episode published?

This episode was published on June 21, 2026.

Can I download this Database Tech with Fexingo: SQL, NoSQL, and Data Storage Conversations episode?

Yes. Use the download control on the episode player to save the publisher-provided media file.