High availability in PostgreSQL depends on replication, failover strategy, and operational discipline. In this session, Boriss Mejías, PostgreSQL Solutions Architect at EDB, walks through designing production-ready Postgres architectures that behave predictably during failures. Topics include HA principles, replication methods, common topologies, infrastructure hygiene, pitfalls, and best practices.
Watch here: https://resources.stormatics.tech/designing-highly-available-postgres-for-continuous-operations

PostgreSQL can run on Kubernetes, but the real question is whether your operating model supports it in production. Kubernetes enables standardization and self service, but adds layers like storage, scheduling, and operators that complicate incident diagnosis. VM based deployments offer simpler tuning, predictable behavior, and clearer failure analysis, with slower provisioning as the trade off. This post explains when each fits, key performance drivers, and real HA needs.
https://stormatics.tech/blogs/postgresql-on-kubernetes-vs-vms-a-technical-decision-guide

PostgreSQL decisions made early, including schema design, indexing, and query patterns, often determine whether an application scales or struggles under real traffic. Stormatics Developer Support gives developers direct access to PostgreSQL experts during design and development. We review schemas, tune complex queries, validate architectural decisions, and help de-risk migrations so your database is production-ready before launch.
https://stormatics.tech/service/postgresql-developer-support

A resilient PostgreSQL backup strategy combines logical and physical backups. Logical backups are portable, selective, and work across major versions, making them ideal for migrations, upgrades, and development workflows. Physical backups capture the full data directory and WAL, enabling point-in-time recovery and incremental restores. Together, they balance mobility and recoverability.
https://stormatics.tech/blogs/postgresql-backup-best-practices

A solid disaster recovery strategy is at the core of business resilience. As PostgreSQL environments grow more complex, the ability to recover quickly and predictably from outages is essential.

In this webinar, Semab Tariq and Warda Bibi share how disaster recovery strategies are designed and evaluated for PostgreSQL production environments, based on real operational scenarios—covering HA vs DR, backup fundamentals, and PostgreSQL-native tools.

Watch the recording:
https://resources.stormatics.tech/webinar-building-a-strong-disaster-recovery-strategy-with-postgresql

Indexes are essential to PostgreSQL performance, yet choosing the wrong one or missing the right one can turn everyday queries into lasting bottlenecks.

On 21 January 2026 at 2 PM GMT, Chris Travers, Principal PostgreSQL Consultant at Stormatics, will run a hands on webinar on advanced indexing. Learn how index types affect production systems, when to use partial and functional indexes, and how GiST and GIN support complex workloads.

Register here: https://resources.stormatics.tech/webinar-advanced-indexes-in-postgresql-smart-indexing-for-faster-queries

PostgreSQL tables rarely hit the 1600 column limit, but wide tables hurt performance much earlier. Fewer rows per page increase I O, updates write full row versions which bloats WAL and replication lag, and schema changes become risky. The real issue is operational stability, not the limit itself.
https://stormatics.tech/blogs/postgresql-column-limits

High availability is critical once an application is in production and user expectations are high. Downtime stops business, impacts customers, and forces teams into reactive mode. Many assume HA requires deep expertise or expensive tools, but this adds unnecessary complexity. By defining tolerable downtime, recovery speed, and acceptable data loss, teams can build reliable systems with open-source solutions without over-engineering.

Read more: https://stormatics.tech/blogs/deploy-production-grade-highly-available-system-with-open-source-tools

Happening tomorrow. Last chance to register. Join Mughees Ahmed and Warda Bibi, PostgreSQL Consultants at Stormatics, on 17 December 2025 at 3:00 PM GMT for a hands on session on unlocking performance in production PostgreSQL. Learn practical tuning of memory, connections, checkpoints, background writer behavior, and autovacuum for real systems.

Register here: https://resources.stormatics.tech/unlocking-high-performance-postgresql

An industry quote claimed a fast-growing AI company moved to MongoDB because PostgreSQL could not scale. But scaling comes from engineering, not branding. When systems struggle, the issue is usually design or operations. Umair Shahid’s blog shows how vertical and horizontal scale, partitioning, and distributed systems keep PostgreSQL strong.

Read the complete post: https://stormatics.tech/blogs/postgresql-mongodb-and-what-cannot-scale-really-means

In a Patroni based PostgreSQL cluster, HAProxy is essential for high availability. When a failover occurs, Patroni promotes a new primary node, but applications can keep sending traffic to the old primary if routing is not updated quickly. HAProxy continuously monitors node health through Patroni APIs and automatically redirects traffic to the new primary within seconds. This process requires no manual action, keeping applications online and SLAs intact.

Learn more: https://stormatics.tech/service/postgresql-dba-as-a-service

Years of Oracle experience shouldn’t slow your move to PostgreSQL. This one-day intensive training is built for Oracle DBAs who want a practical, production-focused understanding of PostgreSQL. We translate familiar Oracle concepts into how PostgreSQL really handles backups, availability, replication, storage, and daily operations. Registration closes today at 11:59 PM GMT.

Register here: https://resources.stormatics.tech/postgresql-for-oracle-dbas-one-day-intensive-training

A clear understanding of how PostgreSQL handles locking is essential to preventing deadlocks and performance stalls. Locks ensure consistency but can restrict scalability when held too long or used inconsistently. Knowing the lock hierarchy, the difference between implicit and explicit locking, and how to reduce contention helps keep workloads stable under load.
Read the full blog: https://stormatics.tech/blogs/locks-in-postgresql-concurrency

If you're an experienced Oracle DBA transitioning to PostgreSQL, you don’t need to relearn everything, just understand where both systems align and diverge. By popular demand, Stormatics is bringing back its One-Day Intensive PostgreSQL Training for Oracle DBAs, one last time at $150. This instructor-led session focuses on architecture, security, storage, indexing, and backup frameworks so you can confidently run PostgreSQL in production.

Register: https://resources.stormatics.tech/postgresql-for-oracle-dbas-one-day-intensive-training

ORDER BY with LIMIT seems simple, but on large tables it can quietly slow queries. PostgreSQL must sort rows before applying LIMIT, and without an index that sort is costly. In a table of 100000 rows, sorting before returning only five rows took 68 ms. After adding an index, the query used an Index Scan and ran in 0.05 ms. Semab’s blog explains the full example, from sequential scans to how indexing avoids sorting.
Read more here: https://stormatics.tech/blogs/performance-impact-of-using-order-by-with-limit-in-postgresql

A client relied on manual pg_dump backups for an 800GB PostgreSQL database, storing everything on the same server. This created a single point of failure, no point in time recovery, and regular performance issues. We moved them to pgBackRest on a dedicated backup server with automated retention, encrypted off site storage, and full PITR support. Backups are now faster, safer, and easier to manage. Read the blog: https://stormatics.tech/blogs/disaster-recovery-guide-with-pgbackrest

Final call to register for the webinar tomorrow. Semab Tariq and Warda Bibi from Stormatics will lead an exclusive session on achieving 99.99% PostgreSQL uptime with open source tools. They will show how TPA, Patroni, pgbouncer, and Barman support high availability and guide you through deployment practices for dev, staging, and production. Register now: https://resources.stormatics.tech/achieving-postgresql-ha-with-open-source-tools

Join our one-day PostgreSQL training for Oracle DBAs on December 11. This live, hands-on session helps Oracle DBAs and engineers quickly build PostgreSQL skills: covering architecture, setup, security, storage, indexing, backups, and replication. Gain confidence to run PostgreSQL in production.
Limited-time price: $150.
Register: https://resources.stormatics.tech/postgresql-for-oracle-dbas-one-day-intensive-training

Final discounted offering!

Patroni focuses on reliable, automated failover and clean leader election, making it ideal if you want a dedicated, isolated HA solution for PostgreSQL. Pgpool II offers a broader set of features, including connection pooling, load balancing, query routing, and failover. Choosing between them depends on your workload and how much HA complexity you’re willing to manage. Read the full comparison here: https://stormatics.tech/blogs/which-postgresql-ha-solution-fits-your-needs-pgpool-or-patroni

PostgreSQL doesn’t write changes to disk right away. Updates and inserts first live in memory as “dirty pages,” newer than what’s stored on disk. This design improves performance and crash safety, but when dirty pages pile up, they can cause I/O spikes and unpredictable slowdowns.

In this post, Umair Shahid breaks down how PostgreSQL manages dirty pages and shares tuning tips to keep performance steady.

Read more: https://stormatics.tech/blogs/what-are-dirty-pages-in-postgresql