PostgreSQL Slow Query Optimization: Diagnose & Fix in 2 Days

Optimizing Slow PostgreSQL SQL Queries

You wait 20 seconds for a report to load. Users leave, the database is the bottleneck. Typical scenario: one query takes 5 seconds, and there are hundreds like it per minute. We diagnose why and fix it: reduce database response time by 3–5x under load. Diagnostics take a day, optimization a couple more. All changes documented, before/after measurements mandatory.

Slow queries are the main cause of poor UX. 95% of database performance problems are solved by one of four methods: adding an index, rewriting the query, denormalization, or caching. Experience shows that properly optimizing the 10–15 heaviest queries can free up to 40% of server resources. Let's see how to diagnose and fix slow queries in PostgreSQL.

How to Diagnose Slow Queries?

pg_stat_statements is the first extension to enable on production. It collects per-query statistics: total and average time, call count, standard deviation. The coefficient of variation (coeff_var) helps spot queries with unstable plans.

Five-step diagnostic process:

1. Enable pg_stat_statements (if disabled) and collect statistics for a few hours.
2. Run a query for the top 20 by total_exec_time.
3. For each suspicious query, get a plan via EXPLAIN (ANALYZE, BUFFERS).
4. Identify plan nodes: Seq Scan, Nested Loop, Hash Join with Batches > 1.
5. Apply the appropriate optimization: add index, rewrite query, tune work_mem.

-- Enable pg_stat_statements
shared_preload_libraries = 'pg_stat_statements'
pg_stat_statements.max = 10000
pg_stat_statements.track = all

-- Top 20 by total time
SELECT round(total_exec_time::numeric, 2) AS total_ms,
       round(mean_exec_time::numeric, 2) AS mean_ms,
       calls,
       round((stddev_exec_time / mean_exec_time * 100)::numeric, 1) AS coeff_var_pct,
       left(query, 120) AS query
FROM pg_stat_statements
WHERE calls > 100
ORDER BY total_exec_time DESC
LIMIT 20;

coeff_var_pct — coefficient of variation: a high percentage indicates an unstable plan (different parameters yield drastically different times). Then run each suspicious query through EXPLAIN ANALYZE:

EXPLAIN (ANALYZE, BUFFERS, FORMAT TEXT)
SELECT p.*, c.name AS category_name
FROM products p
JOIN categories c ON c.id = p.category_id
WHERE p.status = 'published'
  AND p.created_at > NOW() - INTERVAL '30 days'
ORDER BY p.created_at DESC
LIMIT 50;

Key nodes to watch in the plan:

• Seq Scan on a large table — no index or planner thinks index isn't beneficial.
• Nested Loop with many iterations — N+1 at the SQL level.
• Hash Join with Batches > 1 — insufficient work_mem.
• Sort without Index Scan on the ORDER BY column — no suitable index.

Why Aren't Indexes Used?

Even with an index, the planner may ignore it. Main reasons:

• Function on column in WHERE (e.g., DATE(created_at))
• Low selectivity (index on boolean column with skewed distribution)
• Sort order not matching the index order

Solution: rewrite the query to remove function wrappers and create composite indexes for specific patterns. Column order in composite index: equality conditions first, then range and sort.

Which Anti-Patterns Are Most Common?

-- Bad: SELECT * pulls unnecessary columns; OFFSET increases load; OR doesn't use index; function on column; NOT IN with NULL
SELECT * FROM products WHERE category_id = 5 LIMIT 50 OFFSET 10000;
SELECT * FROM users WHERE email = $1 OR phone = $1;
SELECT * FROM orders WHERE DATE(created_at) = $1;
SELECT * FROM products WHERE id NOT IN (SELECT product_id FROM order_items);

-- Good: only needed columns; keyset pagination; UNION ALL; range condition; NOT EXISTS
SELECT id, title, slug FROM products WHERE (created_at, id) > ($1, $2) ORDER BY created_at DESC LIMIT 50;
SELECT * FROM users WHERE email = $1 UNION ALL SELECT * FROM users WHERE phone = $1 LIMIT 1;
SELECT * FROM orders WHERE created_at >= $1 AND created_at < $2;
SELECT p.* FROM products p WHERE NOT EXISTS (SELECT 1 FROM order_items oi WHERE oi.product_id = p.id);

Compare pagination methods:

Optimizing JOINs: Composite Indexes

-- Add composite index for typical filter
CREATE INDEX idx_orders_user_status_created
    ON orders (user_id, status, created_at DESC);

-- Query uses index scan without Sort
SELECT id, total, status, created_at
FROM orders
WHERE user_id = $1
  AND status = 'completed'
ORDER BY created_at DESC
LIMIT 10;

Column order in index: equality conditions first (user_id = $1, status = 'completed'), then range/sort (created_at DESC).

Tuning work_mem and Using LATERAL

If EXPLAIN ANALYZE shows external merge (Disk: ...) during Sort — increase work_mem for the session:

SET work_mem = '64MB';
-- Run the heavy analytical query

In postgresql.conf it's better to keep work_mem low (default 4–8MB) and raise it for specific queries via SET LOCAL work_mem.

-- LATERAL: for row-dependent subqueries
SELECT u.id, u.email, recent.total
FROM users u
CROSS JOIN LATERAL (
    SELECT SUM(total) AS total
    FROM orders o
    WHERE o.user_id = u.id
      AND o.created_at > NOW() - INTERVAL '30 days'
) AS recent;

LATERAL often yields a better plan than JOIN on an aggregated CTE.

Scope of Work for Optimization

• Audit 10–15 heaviest queries via pg_stat_statements and EXPLAIN ANALYZE
• Rewrite queries to eliminate anti-patterns
• Add and tune indexes (including composite and partial)
• Tune PostgreSQL parameters (shared_buffers, work_mem, effective_cache_size)
• Deliver a report with before/after measurements and recommendations for the team
• Optional: train developers on reading query plans

In one project, we cut query execution time from 4 seconds to 200 ms — that reduced server load and allowed us to avoid an infrastructure upgrade. Optimizing 15 slow queries can free a significant portion of server resources.

Timeline and Pricing

Diagnostics and optimization of 10–15 slow queries — 2–3 days. Deep schema and query audit for a high-load application — 3–5 days. Pricing is calculated individually after scope assessment.

To start a project, contact us via Telegram or email — we'll do a free analysis of the first two queries. Order diagnostics and get a report with before/after measurements. We guarantee a measurable reduction in query time of at least 30% — we fix results before and after optimization.

Backend Development Services: Laravel, Node.js, Go, Django, PostgreSQL

On a production server at 3:14 AM, the Laravel Jobs queue stopped processing. 40,000 unprocessed jobs in Redis. Cause: worker crashed due to a memory leak in one of the Jobs (leak via a static variable in an Eloquent observer), supervisor didn't restart it because of misconfigured stopwaitsecs. This is not a hypothetical scenario — it's Tuesday. We analyzed such an incident on a project with 500 RPS load: diagnosis took 4 hours, fix — 20 minutes. So you don't lose money on downtime, we offer backend development services with a focus on production-grade reliability. We'll assess your project in 2 days.

Backend is what works when no one is watching. Or doesn't work. We guarantee you'll have the first option.

How do we ensure production-grade reliability from day one?

What we do correctly from day one

Service Layer over Fat Controllers. Controller receives HTTP request, validates it via Form Request, passes data to Service, returns response. Business logic in Service, not Controller. This sounds trivial, but most legacy projects have controllers with 500 lines and SQL queries inside.

Repository Pattern we use cautiously. If you just wrap Model::where(...) in a repository method — that's boilerplate without benefit. Repository is justified when: you need to abstract from the data source (DB + cache + external API) or when query logic is complex enough to isolate.

Jobs, Events, Listeners. Everything that can be async — make async. Sending email, PDF generation, external API sync, aggregate recalculation — into Queue. Laravel Horizon for queue monitoring in Redis: see throughput, failed jobs, processing time per queue.

How Octane handles high load

Laravel Octane with RoadRunner or Swoole keeps the app in memory between requests — removes bootstrap overhead (config loading, class autoloading) on each HTTP request. Gain: 3–8x on synthetic benchmarks, 2–4x on real applications. Important: no state between requests in static variables — that leads to exactly the incidents from the beginning. We use this in projects with >1000 RPS.

What to do about N+1 queries

N+1 is the most common cause of slow pages in Laravel apps. Standard story: page worked fine on dev with 10 records, on production with 10,000 — 8-second load.

Laravel Debugbar in dev environment shows the number of queries per page. More than 20 queries per page — signal for audit.

Model::preventLazyLoading(! app()->isProduction());

Telescope for profiling in staging: logs all queries, jobs, mail, notifications with time detail. Numbers: after implementing eager loading, page load time drops from 8s to 0.3s — 27 times faster.

PostgreSQL: indexes that are actually needed

PostgreSQL 14+ is the primary DB on all projects. We use PgBouncer + PostgreSQL combination. 10+ years experience, more than 50 backend projects, 5 years on the market.

How PostgreSQL helps avoid slow queries

Composite indexes for frequent WHERE + ORDER BY. If you have WHERE user_id = ? AND status = ? ORDER BY created_at DESC — you need (user_id, status, created_at DESC). A separate index on (user_id) doesn't help much with sorting.

Partial indexes. If 95% of queries go with WHERE status = 'active':

CREATE INDEX idx_orders_active ON orders (created_at DESC)
WHERE status = 'active';

The index is small, fast, covers the main load.

GIN indexes for JSONB and arrays. @> operator without GIN index — seq scan. With index — fast even on millions of rows.

GIN for full-text search. to_tsvector + GIN instead of LIKE '%query%'. LIKE without index is always seq scan. With pg_trgm extension and gin_trgm_ops — supports LIKE with index, useful for CRM search by partial match.

Connection pooling: why it's more important than it seems

Rails, Laravel, Django open a new connection to PostgreSQL for each PHP/Python process. With 100 workers — 100 connections. PostgreSQL starts degrading from 200–300 active connections — overhead on connection management becomes significant.

PgBouncer — connection pooler in front of PostgreSQL. Transaction pooling mode: connection to PostgreSQL is occupied only during a transaction, returned to pool between requests. 1000 application workers → 20–50 actual connections to PostgreSQL. This reduces latency by 40% and hosting costs by 30%.

Node.js with Fastify: when it's better than Laravel

Node.js is justified for:

• Realtime: WebSocket servers, Server-Sent Events, chat, live updates
• Streaming: large files, video, streaming data
• High I/O concurrency: many parallel requests to external APIs without heavy business logic
• Serverless: Lambda/Cloud Functions — Node.js starts faster than PHP

Fastify over Express: 2–3 times faster on benchmarks, built-in JSON Schema validation, better TypeScript support, plugin architecture.

Typical realtime architecture: Laravel — core business logic and REST API. Node.js + Socket.io or ws — WebSocket server. Laravel publishes events to Redis Pub/Sub, Node.js subscribes and broadcasts to clients. This separation allows scaling the WebSocket server independently of the main app.

Go: microservices and high load

Go we use for:

• High-load microservices (>10,000 RPS)
• Background workers with strict latency requirements
• DevOps tools and CLI
• gRPC services in microservice architecture

Goroutines — thousands of times cheaper than OS threads. 10,000 concurrent connections on Go is normal on one server.

But Go is not a silver bullet. Development is slower than Laravel: more boilerplate, no ORM at Eloquent level, error handling with if err != nil everywhere. Justified only when performance is a real requirement, not an assumption.

Django and Python backend

Django with DRF (Django REST Framework) — for tasks where Python is needed: ML pipelines, data processing, integrations with AI tools.

Celery for background tasks — similar to Laravel Queue but more complex to configure. Celery Beat for cron tasks.

Django ORM vs raw SQL: ORM is convenient for CRUD. For analytical queries with multiple JOINs, window functions, and CTEs — connection.execute() with raw SQL is more readable and predictable.

Redis: not just cache

Redis in our projects plays multiple roles:

Redis Cluster for horizontal scaling. Sentinel for automatic failover on standalone setups.

Deployment and infrastructure

Docker + docker-compose — standard for local development and production. Each service in a container: PHP-FPM/Octane, Nginx, PostgreSQL, Redis, Queue Worker, Scheduler.

CI/CD via GitHub Actions:

1. Run tests (PHPUnit / Pest, Vitest, Playwright)
2. Build Docker image
3. Push to Container Registry
4. Deploy: docker pull → docker-compose up -d on server, or Kubernetes rolling update

Zero-downtime deploy for Laravel: php artisan down --secret=TOKEN is not needed with proper configuration. Strategy: new container starts next to the old one, Nginx switches traffic after health check, old container stops.

Monitoring: Sentry for exception tracking with alerting in Slack/Telegram. Grafana + Prometheus (or Grafana Cloud) for metrics: CPU, memory, request rate, queue depth, database connection count. Alerts on: error rate > 1%, p99 latency > 2s, queue depth > 1000 jobs.

What's included in turnkey work

• Architecture design (API documentation, DB schema, service diagram)
• Implementation according to agreed specification with code review
• CI/CD, monitoring, alerting setup
• Load testing (k6, wrk) with report
• Handover of source code, access, deployment instructions
• Training of customer's team (2-3 sessions)
• Warranty support for 1 month after delivery

Timeline benchmarks

Pricing is calculated individually after analyzing load, integrations, and business logic. Contact us for a free audit of your current backend — get an optimization plan in 2 days. Request a consultation.