CHECK Constraint | PostgreSQL Tutorial

CHECK Constraint in Database Constraints helps you write SQL that is easier to test, review, and operate at scale.

Introduction to CHECK Constraint

Use CHECK Constraint to enforce integrity rules directly in the database.

Commonly paired with: FROM, JOIN, WITH, INSERT.

Practical examples with CHECK Constraint in PostgreSQL

Reference pattern: start from canonical syntax and keep it explicit.

ALTER TABLE orders
ADD CONSTRAINT orders_total_amount_check
CHECK (total_amount >= 0);

Production-style scenario: apply the same concept to realistic application data.

BEGIN;
ALTER TABLE orders ADD COLUMN IF NOT EXISTS updated_at TIMESTAMPTZ DEFAULT now();
CREATE INDEX IF NOT EXISTS idx_orders_updated_at ON orders (updated_at DESC);
COMMIT;

Additional example: use a variation to validate behavior and edge cases.

ALTER TABLE orders
ADD CONSTRAINT orders_total_nonnegative CHECK (total_amount >= 0);

Production tips

Prefer explicit column lists and deterministic ordering when results feed APIs or batch jobs.
Validate plans with EXPLAIN before adding indexes, then re-check after schema changes.
Keep DDL, data backfills, and cleanups in transactions when possible to avoid partial state.
Use isolated environments for risky changes so query tuning and schema experiments stay safe.

Vela workflow tip

Test this pattern in an isolated branch database, share the result with your team, and promote only after query plans and row counts look correct.

Reference: PostgreSQL official documentation.