MinervaDB

Enterprise Database Consulting, 24x7 Support and Remote DBA

  • MinervaDB
    • GCC Data Leadership
    • For CTOs
    • For CIOs
    • Full-Stack Optimization
    • MinervaDB University
    • Partner Network
  • Engineering
    • Data Analytics Platform Engineering
    • Fractional CDO
    • Data Science & AI
    • Cloud FinOps
      • MinervaDB Privacy Policy
    • Data Modernization
    • Databricks
    • Snowflake
    • Microsoft Azure
    • AWS
    • Google Cloud
    • AI and Vector Data
    • MySQL
    • PostgreSQL
    • PostgreSQL on Kubernetes
    • SQL Server Consulting
    • MariaDB Consulting
    • MongoDB Consulting
    • Ticketing System
  • Support
    • Enterprise Support
    • 24/7 Emergency DBA
    • PostgreSQL Support
    • MySQL Support
    • MariaDB Support
    • SQL Server Support
    • Db2 LUW & z/OS Support
    • Oracle Database, Exadata & OCI Support
    • MongoDB Support
    • NoSQL
    • Kafka Support
    • Cloud Native
    • Analytics & DWH
    • Data Security
  • Remote DBA
    • 24*7 Emergency DBA
    • PostgreSQL DBA
    • 24/7 MySQL DBA
    • 24/7 MariaDB DBA
    • NoSQL Services
    • MongoDB Services
  • Blog
    • MinervaDB Blog
  • Careers
  • Contact
    • MinervaDB Contacts
    • Book an Appointment
    • MinervaDB FAQ
    • Cookie Policy
    • MinervaDB Privacy Policy
  • Facebook
    • Data Ops. Geek
  • Twitter
    • @MinervaDB
    • @ShivIyer
    • @ChistaDATA
  • LinkedIn
    • Shiv Iyer
  • GitHub
    • @ShivIyer
HomePostgreSQL Performance

PostgreSQL Performance

Oracle Exadata to PostgreSQL 18 Migration
Case Studies

Oracle Exadata to PostgreSQL 18 Migration: An Airline Operations Case Study from the MinervaDB Data Migration Team

This is the MinervaDB Data Migration Team's write-up of an Oracle Exadata to PostgreSQL 18 migration for an airline operations platform: crew scheduling, flight status, aircraft rotation and the reporting that hangs off them. The [...]
pgvector on RDS deployment patterns: coupled, sidecar and split architectures with HNSW memory sizing
AI

pgvector on RDS: What CTOs Should Know Before Building AI Features on Their OLTP Database

pgvector on RDS is the fastest path to shipping an AI feature, and it is also one of the quickest ways to turn a healthy transactional database into a latency incident. Both statements are true [...]
PostgreSQL 18 vacuum tuning diagram showing the autovacuum decision pipeline, new PostgreSQL 18 parameters and per-table policy tiers
PostgreSQL

Your Engineers Shouldn’t Be Doing PostgreSQL 18 Vacuum Tuning at Midnight

PostgreSQL 18 vacuum tuning is a design activity that belongs in a change review, next to your schema migrations and your capacity model. In most engineering organisations it is still handled somewhere else entirely: at [...]
Redis 8.8 cache tier cutting time to result for distributed PostgreSQL query performance in SaaS platforms - hourglass on calendar symbolizing query latency and TTL-based caching
Database Performance

How Redis 8.8 Improves Distributed PostgreSQL Query Performance in SaaS Platforms

Redis 8.8 improves distributed PostgreSQL query performance in SaaS platforms: kvobj memory savings, INCREX rate limiting, hot-key telemetry and a measured cache-aside design.
[...]
PostgreSQL

PostgreSQL 18 Performance Internals: Optimizer and Indexing Advancements

PostgreSQL 18 performance internals deep dive: async I/O, B-tree skip scan, self-join elimination and planner rewrites — verified with real EXPLAIN output on 18.4.
[...]
PostgreSQL Support diagram of the query lifecycle from parse to execute with planner inputs, pg_stat_statements instrumentation and a wait event triage table
MinervaDB

Optimizing SQLs in PostgreSQL 18.4: 12 Proven Techniques for Peak Performance

A practical field manual for optimizing SQLs in PostgreSQL 18.4: EXPLAIN with buffers, B-tree skip scans, asynchronous I/O, statistics, join tuning, six animated diagrams and seven premium diagnostic scripts.
[...]
PostgreSQL Replication Lag
PostgreSQL

Troubleshooting PostgreSQL Streaming Replication Lag in Production

PostgreSQL replication lag troubleshooting: measure send, flush and replay lag via pg_stat_replication, isolate the bottleneck stage, and fix it.
[...]
PostgreSQL Index Bloat
Indexing

Detecting and Fixing PostgreSQL Index Bloat with REINDEX CONCURRENTLY

PostgreSQL index bloat: measure it with pgstattuple, understand why B-trees inflate, and rebuild online with REINDEX CONCURRENTLY without downtime.
[...]
PostgreSQL lock contention featured image for the MinervaDB pg_locks deep dive, showing a three-step blocking chain
Database Performance

Resolving PostgreSQL Lock Contention: A pg_locks Deep Dive

PostgreSQL lock contention resolved: read pg_locks correctly, trace blocking chains, fix deadlocks, and design DDL that never queues production.
[...]
PostgreSQL Wait Events
Monitoring

PostgreSQL Wait Event Analysis: Finding Bottlenecks with pg_stat_activity

PostgreSQL wait events explained: sample pg_stat_activity, interpret Lock, LWLock, IO and Client waits, and turn wait profiles into targeted fixes.
[...]

Posts pagination

1 2 … 33 »

Search MinervaDB Blog 🔎

Tell us how we can help!

Loading

★Read this WARNING★

* Everything changes over time – Our blogs/posts and comments changes over time, That’s how it should be! Whatever we comment from MinervaDB Inc. Teams (including Shiv Iyer) and other stakeholders or guest bloggers posted here are never permanent, These things worked for us. But, there is no guarantee they will work for you too, When using the recommendations from ChistaDATA or MinervaDB or MinervaSQL or any other online resources / Google,  You must test the advice before applying them to your production systems, and always invest for a robust Database DR solution, Thank you for understanding. 

Recent Posts ✏

  • Expensive SQL on Exadata 26.1: Read the Offload Numbers Before You Build the Index
  • SQL Server 2025 Expensive Queries: 7 Proven Ways to Find and Fix Them by Latency and Resource Cost
  • Db2 13 for z/OS Index Efficiency: 8 Proven Troubleshooting Techniques
  • AlloyDB Pricing and Internals: 2026 FinOps Best Practices Guide
  • Google AlloyDB Architecture, Internals and Performance: 2026 Best Practices Guide

☎ Contact Global Sales (24*7)

📞 (844) 588-7287 (USA)

📞 (415) 212-6625 (USA)

 

☎ TOLL FREE PHONE (24*7)

(844) 588-7287 

📌 Our Support Channels (24*7)

✔ Email
✔ IRC
✔ Phone
✔ Ticketing System

🚩 MinervaDB FAX

+1 (209) 314-2364

Corporate Address: California

MinervaDB Inc.
440 N BARRANCA AVE #9718 COVINA,
CA 91723
════════════════════════════════
Email: contact@minervadb.com

Corporate Address: Delaware

MinervaDB Inc.,
PO Box 2093 PHILADELPHIA PIKE #3339
CLAYMONT, DE 19703
════════════════════════════════

Email: contact@minervadb.com

📨 Contact MinervaDB (24*7)

 Email – contact@minervadb.com 

(We are online 24*7)

☛ Contact Shiv Iyer
▬▬▬▬▬▬▬▬▬▬▬▬▬
 Email – shiv@minervadb.com

HOW CAN WE HELP?

We are committed to building Optimal, Scalable, Highly Available, Reliable, Fault-Tolerant and Secured Database Infrastructure Operations for WebScale to our customers globally

📨 Contact MinervaDB Support (24*7)

✔ Support (24*7) – support@minervadb.com

✔ Google Hangouts – support@minervadb.com

(for emergency support and quick response)

💲Flexible Payment

✔ Wire

✔ PayPal

✔ Credit / Debit Cards

✔ Cheque

✔ Cash

★ Discounts ★

Discounts are applicable only for multi-year contracts / long-term engagements, We don’t hire low-quality and cheap rookie consultants to manage your mission-critical Database Systems Infrastructure Operations and so our consulting rates are competitive. Being a virtual corporation (no physical offices anywhere in the world), whatever you pay go directly to our consultant’s fee. It’s impossible for us to offer you low-cost consulting, support and remote DBA services with elite-class team, Thanks for understanding and doing business with MinervaDB.

PostgreSQL is a registered trademark of the PostgreSQL Community Association. ClickHouse is a registered trademark of ClickHouse, Inc. MongoDB is a registered trademark of MongoDB, Inc. Couchbase is a registered trademark of Couchbase, Inc. Redis is a registered trademark of Redis Ltd. Apache Cassandra is a registered trademark of the Apache Software Foundation. Milvus is a registered trademark of Zilliz. MinIO is a registered trademark of MinIO, Inc. Amazon Redshift and Amazon Aurora are registered trademarks of [Amazon.com](http://amazon.com/), Inc. Google Cloud is a registered trademark of Google LLC. Snowflake is a registered trademark of Snowflake Inc. Databricks is a registered trademark of Databricks, Inc. MySQL and InnoDB are registered trademarks of Oracle Corporation. MariaDB is a trademark of MariaDB Corporation Ab. All other trademarks are the property of their respective owners. Copyright © 2010–2026. All Rights Reserved by MinervaDB®.

Table of Contents

×
  • How Wait Event Sampling Works — and Its One Big Caveat
  • Lock Waits: Someone Is Holding What You Need
  • LWLock Waits: Internal Contention
  • IO Waits: Reading the Storage Story
  • Client and IPC Waits: The Database Waiting on Everyone Else
  • From Wait Profile to Action: A Worked Triage
  • Attributing Waits to Queries: Joining the Two Telemetry Planes
  • Building the Wait Dashboard That Ops Actually Uses
  • Second Worked Case: The Invisible Checkpoint Storm
  • Wait Signatures of Maintenance and Bulk Operations
  • Version Landscape: What Changed Where
  • Quick Reference
  • Frequently Asked Questions (FAQ)
    • Why doesn’t PostgreSQL record cumulative wait time natively?
    • What sampling interval is right?
    • Are LWLock waits ever “normal”?
    • How do wait events relate to EXPLAIN ANALYZE?
    • Do wait event names change between versions?
  • Turn Wait Data into an Operating Practice
  • PostgreSQL Wait Event Analysis: Reference Taxonomy and Further Reading
    • PostgreSQL Wait Event Analysis Checklist
→ Index