Resources / PostgreSQL Tutorial

Correlated Subquery

Correlated Subquery explained with practical SQL patterns, edge cases, and production-ready guidance.

10 min read

Spin up a Postgres database in 20 seconds with Vela.

Try Vela Sandbox

Correlated Subquery in Subquery helps you write SQL that is easier to test, review, and operate at scale.

Introduction to Correlated Subquery

Use Correlated Subquery to embed dependent logic inside larger queries.

Commonly paired with: SELECT, FROM, WHERE, WITH.

Practical examples with Correlated Subquery in PostgreSQL

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

SELECT c.customer_id
FROM customers c
WHERE EXISTS (
  SELECT 1
  FROM orders o
  WHERE o.customer_id = c.customer_id
    AND o.total_amount > 1000
);

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

SELECT
  o.order_id,
  o.total_amount,
  o.placed_at
FROM orders o
WHERE o.placed_at >= now() - interval '30 days'
ORDER BY o.placed_at DESC
LIMIT 50;

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

SELECT current_database(), current_user, now();

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.

Continue through the next items in Subquery: ANY Operator .

Related: Subquery ANY Operator ALL Operator