UUID, Enum & Domain Types
When enums help and when lookup tables win. Practical PostgreSQL patterns for production queries.
Search across all documentation pages
When enums help and when lookup tables win. Practical PostgreSQL patterns for production queries.
CREATE TYPE app.status AS ENUM ('pending','active','closed');
CREATE DOMAIN app.positive_int AS int CHECK (VALUE > 0);When to reach for this: This pattern appears in application or reporting SQL you maintain.
CREATE TABLE app.cases (
id uuid PRIMARY KEY DEFAULT gen_random_uuid(),
status app.status NOT NULL DEFAULT 'pending',
priority app.positive_int NOT NULL
);What this demonstrates:
| Alternative | Use When | Don't Use When |
|---|---|---|
| ORM query builder | Team standardizes on one stack | Complex SQL becomes opaque |
| Materialized view | Repeat expensive aggregates | Needs refresh strategy |
| Warehouse replica | Heavy BI scans | Not for OLTP latency |
Use multiline template strings or SQL files; lint in CI.
When you need unique rows without aggregates.
Sort can use index order if query matches index columns.
Stack versions: This page was written for PostgreSQL 18.4 (stable 18, maintenance 17), pgvector 0.8+, PgBouncer 1.x, Patroni 3.x, and PostGIS 3.5+.
Reviewed by Chris St. John·Last updated Jul 19, 2026