Upsert | PostgreSQL Tutorial

Upsert in Modifying Data helps you write SQL that is easier to test, review, and operate at scale.

Introduction to Upsert

Use Upsert to change data safely with predictable write behavior.

Commonly paired with: SELECT, FROM, WHERE, ORDER BY.

Practical examples with Upsert in PostgreSQL

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

INSERT INTO feature_flags (name, enabled)
VALUES ('new_checkout', true)
ON CONFLICT (name)
DO UPDATE SET enabled = EXCLUDED.enabled;

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

BEGIN;
UPDATE inventory SET quantity = quantity - 1 WHERE sku = 'sku_123';
INSERT INTO inventory_audit (sku, change_reason) VALUES ('sku_123', 'purchase');
COMMIT;

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

BEGIN;
INSERT INTO audit_log (event_type, payload)
VALUES ('data_change', jsonb_build_object('table', 'orders'));
COMMIT;

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.