DB Performance Monitoring: pg_stat_statements & Slow Query Log

Imagine this: your online store's database is overloaded; every 5 minutes pages take 10 seconds to load, and during peak sales the site goes down. You check the server—CPU is free, memory has headroom, but queries are still slow. Without database performance monitoring, slow queries go undetected. We configure pg_stat_statements and the slow query log, connect Prometheus with Grafana, and you see precise metrics: cache hit rate, replication lag, the heaviest queries. In 2 days you get dashboards that show in real time which queries are slowing the system. This isn't a one-time check—it's continuous control.

We've encountered a case where one slow JOIN due to a missing index consumed 40% of database time. After setting up monitoring, the client found and fixed the issue within an hour. Operational cost savings reach 30%—equivalent to $15,000 annually for a medium-sized e-commerce store. We'll assess your project for free—reach out to us.

How pg_stat_statements Helps Identify Query Bottlenecks

The pg_stat_statements extension accumulates statistics for each unique query: execution time, number of calls, standard deviation. Configuration is minimal:

shared_preload_libraries = 'pg_stat_statements'
pg_stat_statements.max = 10000
pg_stat_statements.track = all
pg_stat_statements.track_utility = off

After restart, create the extension and run queries to find problems:

-- Top by total time
SELECT left(query, 120) AS query, calls,
       round(total_exec_time::numeric / 1000, 1) AS total_sec,
       round(mean_exec_time::numeric, 1) AS avg_ms,
       round(stddev_exec_time::numeric, 1) AS stddev_ms,
       round(rows::numeric / nullif(calls, 0), 0) AS rows_per_call
FROM pg_stat_statements
WHERE dbid = (SELECT oid FROM pg_database WHERE datname = current_database())
  AND calls > 10
ORDER BY total_exec_time DESC
LIMIT 20;

-- Queries with high time variance
SELECT left(query, 120) AS query, calls,
       round(mean_exec_time::numeric, 1) AS avg_ms,
       round(stddev_exec_time::numeric, 1) AS stddev_ms,
       round(stddev_exec_time / nullif(mean_exec_time, 0) * 100, 1) AS cv_pct
FROM pg_stat_statements
WHERE calls > 100
ORDER BY cv_pct DESC
LIMIT 10;

On one project, we found a query that averaged 2.3 seconds and accounted for 15% of total DB time. After adding an index, the time dropped to 15 ms—a 153x improvement. pg_stat_statements documentation confirms this is the fastest way to get an aggregated picture. Compared with the slow query log:

Together, they help locate bottlenecks 3 times faster than manual log inspection.

Why the Slow Query Log Matters for MySQL

In MySQL, enable the slow query log with a 1-second threshold and logging queries without indexes:

slow_query_log = ON
slow_query_log_file = /var/log/mysql/slow.log
long_query_time = 1
log_queries_not_using_indexes = ON
min_examined_row_limit = 1000
log_slow_rate_limit = 100

A typical case: a query without an index scanned 500,000 rows, taking 4.2 seconds. After analysis, we added a composite index, cutting time to 0.03 seconds—a 99.3% reduction. We analyze using Percona Toolkit:

pt-query-digest --since="1h ago" --limit 20 --output report /var/log/mysql/slow.log

This gives count, avg/max time, and rows examined for each unique query.

Metric Monitoring: Prometheus + Grafana

For PostgreSQL, we use postgres_exporter; for MySQL, mysqld_exporter. Exporter configuration is standard and can be set up within an hour. Key metrics and alerts:

Example alerting rules:

groups:
  - name: postgresql
    rules:
      - alert: PostgreSQLSlowQueries
        expr: rate(pg_stat_statements_total_exec_time_seconds_total[5m]) > 10
        for: 2m
      - alert: PostgreSQLHighConnections
        expr: pg_stat_activity_count > pg_settings_max_connections * 0.8

You can import ready-made Grafana dashboards (ID 9628 for PostgreSQL, 7362 for MySQL).

What's Included in Our DB Monitoring Setup

We deliver complete documentation: access configuration, deployment instructions, and runbook for alerts. After implementation, you get:

• Configured exporters for PostgreSQL and MySQL.
• Grafana dashboards with key metrics (cache hit rate, replication lag, top queries).
• Custom alerts sent to Telegram or Slack.
• Team training on interpreting metrics and responding to alerts.
• Daily pgBadger reports on slow queries.

This lets your team maintain database performance independently. The implementation cost is $2,500, and it pays for itself within 2 months by reducing downtime costs by an average of $10,000 per year. Get a consultation—we'll assess your project in 1 hour.

Stages of DB Monitoring Setup

1. Analysis: Collect current metrics, identify bottlenecks via logs and statistics.
2. Configuration: Set up pg_stat_statements and slow_query_log with optimal parameters.
3. Deployment: Deploy Prometheus exporters (postgres_exporter, mysqld_exporter).
4. Dashboards: Create custom Grafana dashboards for cache hit rate, replication lag, top queries.
5. Alerts: Configure Alertmanager rules with notifications to Telegram/Slack.
6. Integration: Set up pgBadger for daily reports and train your team.
7. Documentation: Provide configuration docs and runbook for alert responses.

Common Mistakes in DB Monitoring Setup

• Not setting pg_stat_statements.track_utility = off—cluttering statistics with internal queries.
• Forgetting log_line_prefix in MySQL—losing context in slow logs.
• Using the same dashboard for all databases—ignoring replication and sharding specifics.
• Not adding burst handling in Alertmanager—getting spam from short spikes.

We fix these issues during implementation. Our engineers have 5+ years of experience in PostgreSQL and MySQL administration and are Prometheus certified. With over 10 performance optimization projects, we guarantee results. After implementing monitoring, clients save up to 40% of diagnosis time (approximately $8,000 in labor savings per year) and cut downtime by half. Order DB monitoring setup—we'll identify bottlenecks in 2 days.

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.