Brian Fehrle presents on modernizing databases in Postgres World Webinar

🚀 #Day66 of #100DaysOfDevOps — MySQL Deployment on Kubernetes Today, I worked on deploying a MySQL server within a Kubernetes cluster using Persistent Volumes, Secrets, and NodePort Services. The setup involved: 🔹 Defining a PersistentVolume (PV) and PersistentVolumeClaim (PVC) for data persistence. 🔹 Creating Kubernetes Secrets to securely manage credentials (root password, user credentials, and database name). 🔹 Deploying a MySQL container with environment variables mapped from the secrets. 🔹 Exposing it via a NodePort Service for external access. This exercise reinforced how Kubernetes integrates storage management and secret handling to create secure, scalable database deployments. #DevOps #Kubernetes #MySQL #CloudNative #100DaysOfCloud #Containers

Upgrading PostgreSQL: A potentially multi-million dollar decision that doesn't have to happen yet. Your PostgreSQL version is reaching end-of-life. Your team estimates 18 months and significant budget to upgrade across hundreds of databases. Sound familiar? PgLTS from Command Prompt, Inc. extends PostgreSQL support by 3 additional years, giving you eight years total instead of five years. What this means: — Time to plan properly instead of rushing — Budget spread over additional years — FedRAMP compliance maintained — Support for PostgreSQL 12+ Think of it like extending a lease while you plan your next building—except for your database infrastructure. Learn more at https://lnkd.in/gpiMGVam #PostgreSQL #Database #EnterpriseTech #DevOps  #EnterpriseIT

🚀 Achieving Seamless PostgreSQL Replication with Pgpool-II: Load Balancing, Failover & Smart Query Routing Just wrapped up a deep-dive setup for PostgreSQL Master-Replica Replication integrated with Pgpool-II — and the results are 🔥 In this setup: 🧠 Pgpool-II sits between your application and PostgreSQL nodes. ✍️ All write queries are automatically routed to the Master. 📖 All read queries are load-balanced across the replicas for better performance. ⚙️ It handles automatic failover, ensuring continuous availability even if the master goes down. 💨 Plus, it provides connection pooling, reducing connection overhead and improving throughput. This architecture enables: ✅ High availability ✅ Efficient resource utilization ✅ Transparent failover ✅ Improved scalability Check out the Medium article- https://lnkd.in/gY4S256A #PostgreSQL #PgpoolII #DatabaseArchitecture #Replication #Failover #LoadBalancing #DevOps #BackendEngineering

PostgreSQL 18 was officially released on September 25, 2025, and it brings one of the biggest architectural upgrades in years, a next-generation asynchronous I/O subsystem. Before PostgreSQL 18, most disk I/O was synchronous, and now the new async I/O layer can fetch data without blocking the main process and intelligently batch operations. This upgrade results in meaningful real-world performance gains: ✅ Faster queries, especially heavy-read workloads ✅ Higher throughput under concurrency ✅ Better hardware utilization without extra tuning For teams building scalable products, this means smoother performance during peak usage — without over engineering infrastructure. If you would like to better understand how this upgrade can impact your architecture and improve scalability in your stack, feel free to reach out to us at hello@whitecodelabs.com #PostgreSQL #CTO #CIO #CEOPerspective #StartupTech #Scalability #CloudArchitecture #Databases #OpenSource #BackendEngineering

🔄 Is Your Database Ready for Zero Downtime? Data availability isn't optional anymore—it's critical. Our latest blog breaks down PostgreSQL replication in a way that's both comprehensive and actionable. 🔎 What You'll Learn: 🔺How Write-Ahead Logging (WAL) powers PostgreSQL replication 🔺Streaming vs Logical Replication—which one fits your needs? 🔺Step-by-step configuration guides with real commands 🔺Advanced topologies: Cascading & Bi-Directional Replication (BDR) 🐘 Whether you're building for high availability, read scalability, or disaster recovery, this guide has you covered. 📖 Read the full blog: https://lnkd.in/gK2UMM4E 💬 Have questions about implementing replication for your systems? Let's talk! 📞 +91-6385312716 | 8870076562 #PostgreSQL #DatabaseReplication #HighAvailability #DevOps #DatabaseManagement

Scaling Postgres 388 is released! In this episode, we discuss PG17 and PG18 benchmarks across storage types, more about Postgres locks, sanitizing SQL and can a faster software & hardware environment cause performance problems? https://lnkd.in/eHXb6uwi #Postgres #PostgreSQL

🚀 New on the DownToZero Blog: Scale-To-Zero PostgreSQL Databases We took our scale-to-zero philosophy one step further — all the way to PostgreSQL. By combining systemd socket activation and Docker Compose, we built databases that only run when needed — saving compute, memory, and cost. Discover how it works, when it shines, and where it doesn’t. 👉 https://lnkd.in/eskvCrAP #PostgreSQL #ScaleToZero #CloudComputing #GreenTech #DowntoZero #DevOps #Sustainability

PostgreSQL 18 is almost here, and it’s poised to be a game-changing major release focused squarely on performance and enterprise modernization! This isn't just an incremental update—it tackles long-standing database challenges head-on. Here are the features that have me most excited about the impact on scaling and architecture: Async I/O: A foundational architecture shift that eliminates I/O wait times. Expect dramatic speed-ups for large data scans and critical maintenance operations like VACUUM. UUID v7 (Native Support): Finally solving the index fragmentation problem! By providing time-ordered UUIDs, we now have a truly viable, high-performance option for primary keys, future-proofing your indexing strategy. Skip Scans: Supercharge your composite indexes. You can now efficiently query non-leading columns without resorting to a full table scan, making your current indexes far more flexible and powerful. Virtual Generated Columns: The new default for generated columns. Compute values on-demand without any storage overhead, which is a perfect, efficient solution for complex calculations on JSONB fields. OAuth 2.0 Integration: Built-in, enterprise-grade authentication. Connect to your database using secure tokens from your identity provider instead of managing traditional passwords. This release delivers critical modern capabilities and massive performance gains. A huge thank you to the entire PostgreSQL community and all contributors for this monumental effort! Are you planning your upgrade path yet? I’d love to hear which feature you're looking forward to most! #PostgreSQL #PostgreSQL18 #Database #TechNews #SoftwareDevelopment #DevOps #DataEngineering

Your database keeps hitting disk. Here's why that matters. When PostgreSQL needs data, it looks in shared_buffers first. Think of it as your database's working memory. If the data isn't there, PostgreSQL reads from disk instead. That disk read? It's roughly 100x slower than memory access. The shared_buffers parameter determines how much RAM PostgreSQL dedicates to caching your most-accessed table data. Out of the box, it's often set conservatively low (128MB). That means more disk I/O than necessary. Bumping this value up means: - Query results arrive faster - Your storage subsystem breathes easier - Peak load performance stays consistent This isn't a magic fix for slow queries. But it removes a common bottleneck that trips up growing systems. What's your current shared_buffers setting? Learn more about essential PostgreSQL parameters in the Postgres World webinar, "Proper PostgreSQL Parameters to Prevent Poor Performance," with Grzegorz Dostatni, DBA, at Command Prompt, Inc. Watch at https://lnkd.in/gsEMwwVS #PostgreSQL #DatabasePerformance #DevOps

Last week I upgraded my primary PostgreSQL docker cluster to version 18. There has been a fundamental change to the storage location for the postgres docker image that admins really need to be aware of before upgrading. What this means is that the usual "change the tag and redeploy" upgrade will fail this time. But there's a good reason: this change enables pg_upgrade migrations for all future major releases. I've documented the safe, step-by-step process for this one-time migration to version 18. My guide covers: The 'why' behind the new PGDATA location. How to migrate using pg_dumpall. A safe backup strategy for your old volume. Full article here: https://lnkd.in/euiw4iEA