postgres-column-design

What problem does it solve?

Decide whether a new or evolving schema should store data in a JSONB column or in normalized relational columns, balancing flexibility with queryability, integrity, and performance.

Core Features & Use Cases

• Gate-based decision framework for column shape (Gate 1: Shape, Gate 2: Access, Gate 3: Cost) to decide between JSONB and relational design.
• Clear rules on indexing and query patterns for JSONB (GIN, jsonb_path_ops, expression or partial indexes) and when to stage data.
• Use cases across table design, adding JSONB fields, and reviewing schema changes that introduce JSONB payloads.

Quick Start

Analyze a schema change to decide whether to use JSONB or relational columns, applying the three gates and recommended indexes.