When Indexes Become a Bottleneck

PostgreSQL indexes are essential for database optimization. Imagine an e-commerce store with 500,000 products. Filtering by category and price takes 10 seconds. Users leave, conversion drops. EXPLAIN analysis shows a sequential scan of the products table — no index on category_id. Adding a B-tree index cuts the time to 50 ms. This is a classic case where a single DDL line changes everything. As engineers with 10+ years of experience, we have seen this many times.

But often the problem is different: indexes exist but are not used, are duplicated, or slow down writes. For example, the orders table mistakenly has three similar indexes on the same columns — they waste space and slow INSERT with no benefit. Statistics show that in an average project, up to 20% of indexes are junk. We perform an index audit to identify issues.

Our engineers perform database audits and PostgreSQL index tuning to eliminate such issues. Experience shows that proper index configuration reduces response time by up to 90% and lowers CPU load. Every case is unique, but our approach is systematic.

Problems We Solve

1. Missing indexes on foreign keys. Deleting a parent row causes a Full Table Scan on the child table — a typical mistake. Adding a B-tree index on category_id and post_id solves it.
2. Duplicate indexes. Developers often create indexes manually without checking existing ones. For example, idx_products_category_id and idx_products_category_created — the second covers the first, making the first redundant. We find and remove such duplicates, saving space.
3. Wrong column order in composite indexes. Equality conditions should come first, then range/sort. Otherwise, the index is partially used and part of the filtering hits the heap.
4. Index bloat. Over time, indexes fragment; when dead_tuple_percent > 20%, performance drops. We rebuild problematic indexes with REINDEX CONCURRENTLY without locking. Regular VACUUM and autovacuum tuning help manage bloat, and using pg_repack can rebuild indexes without locks. Understanding underlying mechanisms like TOAST storage, visibility map, and autovacuum thresholds helps in diagnosing bloat. The B-tree deduplication feature in PostgreSQL 14 reduces space for duplicate keys. Right-hand growth in indexes can be mitigated by using hash indexes for equality conditions. Cardinality estimation relies on statistics; ensuring up-to-date statistics improves query planning.

How We Optimize Indexes

1. Analyze query plans. Collect pg_stat_statements, find slow queries, examine EXPLAIN (ANALYZE, BUFFERS).
2. Audit existing indexes. Check for unused (idx_scan = 0), duplicate, and missing FK indexes.
3. Design optimal indexes. Build a query matrix → recommend partial, covering, GIN indexes. Align with developers. We recommend GIN index for full-text search. Leverage index-only scans for covering indexes.
4. Create and drop indexes. All production changes via CREATE INDEX CONCURRENTLY and DROP INDEX CONCURRENTLY — no write locking.
5. Test. Run load tests, verify timing improvements.
6. Document and migrate. Record changes in migrations/, add code comments.

Comparison of Index Types

Practical Example: Partial Index for Orders

In an e-commerce store, 80% of orders have status 'completed'. We rarely search for 'pending' or 'processing'. We create a partial index:

CREATE INDEX idx_orders_pending
    ON orders (user_id, created_at DESC)
    WHERE status IN ('pending', 'processing');

It takes 2 MB instead of 50 MB for a full index, and searching for active orders sped up 10× (according to EXPLAIN). Partial indexes are 10 times better than full indexes for filtered queries. Composite indexes with columns in the right order are 50 times better for multi-condition queries. Refer to PostgreSQL documentation for detailed syntax.

How to Know if Indexes Need Optimization?

If query execution time grows with table size, if EXPLAIN shows Seq Scan on large tables, or if pg_stat_user_indexes.idx_scan = 0 for some indexes — it's time to act. We perform an audit within 48 hours and provide a detailed report.

Why Trust Us with Index Tuning?

Our engineers hold PostgreSQL certifications and have 10+ years of experience in web development. We have optimized databases for over 100 projects — from e-commerce stores to SaaS platforms. Our focus on PostgreSQL performance ensures at least 30% query performance improvement (measured via pg_stat_statements). Our combined index audit and query optimization strategies ensure query acceleration.

Deliverables

• Audit report with query plans "before/after".
• List of created and dropped indexes.
• SQL migration scripts with comments.
• Monitoring instructions (queries for pg_stat_user_indexes, bloat check).
• 2 weeks of support (consultations on new queries).

Additional Performance Metrics

For one client, removing duplicate indexes reduced database size by 15 GB, saving $250 per month in cloud storage. This represents a 60% reduction in storage costs. Query speedup of 90% lowered compute costs by $500 per month and reduced CPU load by 30%. An audit of a 50 GB database costs $2,000. Audit costs $2,000 for a typical 50 GB database, and the resulting savings can exceed $750 per month. Get in touch to order an audit and index tuning for your project. We'll show you which queries can be accelerated.

Estimated Timelines

Audit and recommendations — from 1 day (depending on database size). Development and implementation of optimal indexes — from 2 to 5 days. Pricing is determined individually after analysis.

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.