Postgres and Json - How to get the best of them?
summary
Postgres with JSONB outperforms plain JSON on reads — tests show typical select speedups of around 3× and in some cases 10–15× using GIN indexes; writes and large nested documents suffer big slowdowns because of parsing/TOAST and lack of hot updates. Generated columns plus traditional indexes often beat pure JSONB designs for targeted queries, and mismatched types kill index usage — type conversions can disable indexes. A mixed JSONB+relational design usually works best.
AI-written summary · about
chapters (4)
related talks
05mPostgreSQL JSON JSONB Making the Right Choice for Your Application
49mShould I use JSON in PostgreSQL?
53mNoSQL Best Practices for PostgreSQL
35mLeveraging PostgreSQL 17's JSONB for Enhanced Data Modeling
53mPostgres vs Mongo
42mNoSQL as Not Only SQL
25mJSON in PostgreSQL - evil data type or just needs to be tamed?
14mJSON data structure – the hidden gem inside your database engine