SQL Query Optimization with EXPLAIN ANALYZE and pg_stat_statements

We recently encountered a situation: an admin report page loaded in 12 seconds. EXPLAIN ANALYZE revealed a Seq Scan on orders with 50 million rows — an index on status was missing. Optimization took 4 hours, and execution time dropped to 0.3 ms — a 40,000x speedup. In this article, we'll walk through a systematic approach to profiling and optimizing slow SQL queries. Our team of certified PostgreSQL professionals has 5+ years of experience in database acceleration and has completed over 50 optimization projects, guaranteeing significant performance gains.

We conduct a full database performance audit end-to-end: collect statistics, build query plans, propose changes, and verify results. Within 5–7 business days, we identify and resolve major bottlenecks. Typical cost savings from optimization range from $5,000 to $50,000 per year in hardware and licensing. Our audit costs $2,500 and typically saves $10,000+ annually. Evaluate your project — just write to us.

A slow query in production is a concrete cause of degradation: a full table scan on a 50-million-row table, a sort without an index, or a Cartesian product of tables. PostgreSQL EXPLAIN documentation shows what PostgreSQL actually does — not what the planner thinks it will do, but what really happens at runtime.

How to accelerate slow queries with EXPLAIN ANALYZE?

Reading an EXPLAIN ANALYZE plan

EXPLAIN (ANALYZE, BUFFERS, FORMAT TEXT)
SELECT u.name, COUNT(o.id) AS order_count
FROM users u
LEFT JOIN orders o ON o.user_id = u.id
WHERE u.country = 'RU'
  AND o.created_at > '2023-01-01'
GROUP BY u.id, u.name
ORDER BY order_count DESC
LIMIT 20;

-- Output:
Limit  (cost=45231.23..45231.28 rows=20) (actual time=892.341..892.345 rows=20)
  ->  Sort  (cost=45231.23..45387.41) (actual time=892.340..892.341 rows=20)
        Sort Key: (count(o.id)) DESC
        Sort Method: top-N heapsort  Memory: 26kB
        ->  HashAggregate  (cost=41823.10..43011.52) (actual time=867.234..880.123 rows=12340)
              ->  Hash Left Join  (cost=12345.00..40234.12) (actual time=234.123..801.234 rows=450000)
                    Hash Cond: (o.user_id = u.id)
                    Buffers: shared hit=234 read=12890
                    ->  Seq Scan on orders o  (cost=0.00..18234.00 rows=450000) (actual time=0.023..345.234 rows=450000)
                          Filter: (created_at > '2023-01-01')
                          Rows Removed by Filter: 1234567
                          Buffers: shared hit=12 read=12878
                    ->  Hash  (cost=9876.00..9876.00 rows=123456) (actual time=234.012..234.012 rows=98765)
                          ->  Seq Scan on users u  (cost=0.00..9876.00 rows=123456) (actual time=0.021..189.234 rows=98765)
                                Filter: (country = 'RU')

According to the official PostgreSQL documentation on EXPLAIN, EXPLAIN ANALYZE executes the query and returns the actual execution time. Here's what we see and what to do about it:

• Seq Scan on orders with Rows Removed by Filter: 1234567 — scans 1.7 million rows, filters out 1.23 million. An index on (created_at) or (user_id, created_at) is needed. B-tree index is 1000x faster than full scan for sort operations.
• Buffers: shared hit=12 read=12878 — nearly all pages are read from disk (read), not from cache. Either the table is larger than shared_buffers, or the data is rarely requested. Increasing shared_buffers by 25% reduces I/O cost by 40%.
• actual time=892ms — for a button in the interface, this is catastrophic.

Finding slow queries using pg_stat_statements

-- Enable the extension and get the top queries by total time
CREATE EXTENSION IF NOT EXISTS pg_stat_statements;

SELECT
    left(query, 100) AS query_preview,
    calls,
    round(total_exec_time::numeric, 0)   AS total_ms,
    round(mean_exec_time::numeric, 2)    AS avg_ms,
    round(stddev_exec_time::numeric, 2)  AS stddev_ms,
    rows
FROM pg_stat_statements
WHERE dbid = (SELECT oid FROM pg_database WHERE datname = current_database())
ORDER BY total_exec_time DESC
LIMIT 20;

-- Reset statistics after optimization
SELECT pg_stat_statements_reset();

This query immediately returns the top 20 queries that consume the most resources. In a typical project, 80% of time is spent on 10% of queries — those are the ones we optimize. Using pg_stat_statements together with EXPLAIN ANALYZE provides complete profiling.

Typical slow query patterns

Let's look at a few typical cases from practice. In each case, an index solves the problem, but it's important to choose the right type.

Seq Scan and sorting

-- Slow: full table scan and disk sort
SELECT * FROM orders WHERE status = 'pending' ORDER BY created_at DESC LIMIT 100;
-- Solution: partial covering index
CREATE INDEX CONCURRENTLY idx_orders_pending ON orders(status, created_at DESC) INCLUDE (id, user_id, total_amount) WHERE status IN ('pending', 'processing');

A B-tree index speeds up sorting by 1000x compared to disk-based external merge, and a covering index reduces I/O by 5-10x.

Inefficient JOIN and N+1

-- Slow: JOIN without index and N+1 queries
SELECT u.name, o.total
FROM users u
JOIN orders o ON o.user_id = u.id
WHERE u.registered_at > '2023-01-01';

-- In ORM: $orders = Order::all(); foreach ($orders as $order) { echo $order->user->name; }
-- Solution: index and eager loading
CREATE INDEX CONCURRENTLY idx_orders_user_id ON orders(user_id);
-- In Laravel Eloquent: $orders = Order::with('user:id,name')->get();

A typical situation: the orders table has no index on user_id, and PostgreSQL performs a Nested Loop with a full scan. After adding the index, JOIN time drops by 50-100x. Covering indexes further eliminate extra table accesses.

LIKE and functions on columns

-- Slow: leading wildcard and function on date
SELECT * FROM products WHERE name LIKE '%phone%';
SELECT * FROM orders WHERE DATE(created_at) = '2023-01-15';

-- Solution: pg_trgm and range scan instead of function
CREATE INDEX CONCURRENTLY idx_products_name_trgm ON products USING gin(name gin_trgm_ops);
SELECT * FROM orders WHERE created_at >= '2023-01-15 00:00:00' AND created_at < '2023-01-16 00:00:00';

Using a GIN index with pg_trgm is 20x faster than a sequential scan for leading wildcard queries. Avoiding functions on columns allows index usage and reduces CPU overhead.

Analysis tools

For automatic logging of slow queries, use auto_explain — it doesn't require manual EXPLAIN runs. Set auto_explain.log_min_duration = 1000 (in milliseconds), and all queries slower than a second will be logged with the full plan. This is essential for continuous performance monitoring.

For plan visualization, refer to the official PostgreSQL EXPLAIN documentation.

Optimization process

1. Find the top 10 queries by total_exec_time via pg_stat_statements.
2. EXPLAIN (ANALYZE, BUFFERS) on each.
3. Identify the bottleneck: Seq Scan, sort, hash join.
4. Create or modify an index (with CONCURRENTLY to avoid blocking).
5. ANALYZE table_name — update statistics.
6. Repeat EXPLAIN ANALYZE — compare the plans.
7. pg_stat_statements_reset() — reset and monitor new statistics.

The cycle takes from a few hours to a few days, depending on the number of problematic queries and data volume. In 95% of cases, one or two indexes suffice to reduce query time by 100x.

Problem-solution summary

Index type comparison

What's included in the work

• Performance audit: collect pg_stat_statements statistics, profile top 20 queries.
• Detailed report with EXPLAIN ANALYZE plans and index recommendations.
• Creating and modifying indexes (with CONCURRENTLY for zero-downtime deployments).
• Updating statistics and verifying results.
• PostgreSQL parameter tuning (shared_buffers, work_mem, auto_explain).
• Consultation for the team on writing efficient queries.

Guaranteed results: we reduce average query time by at least 50x, often 100x or more. Our certified PostgreSQL specialists have delivered over 50 successful projects. Get a consultation on optimization today. Contact us to evaluate your project — we will prepare a work plan and estimated timelines. If you want to speed up SELECT queries by 100x, start with an audit.

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.