Mafiree logo
  • About
  • Services
  • Blogs
  • Careers
  • Products
    • orbit logo Orbit
    • streamer logo Xstreami
  • Contact
Schedule a Call
Menu
  • About
  • Services
  • Blogs
  • Careers
  • Products
    • orbit logo Orbit
    • streamer logo Xstreami
  • Contact
  • Schedule a Call
Database
Database Managed Database Services
MySQL MySQL
MySQL Consulting
MySQL Migration Services
MySQL Optimization & Query Tuning
MySQL Database Administration
MySQL Backup & Recovery
MySQL Security & Maintenance
MySQL Cloud Services (AWS RDS, Aurora, Google Cloud SQL, Azure)
MySQL for Ecommerce
MySQL High Availability & Replication
MongoDB MongoDB
MongoDB Consulting
MongoDB Migration Services
MongoDB Optimization & Query Tuning
MongoDB Database Administration
MongoDB Backup & Recovery
MongoDB Security & Maintenance
MongoDB Cloud (Atlas)
MongoDB Solutions by Industry
MongoDB High Availability & Replication
PostgreSQL PostgreSQL
PostgreSQL Consulting
PostgreSQL Migration & Upgrades
Performance Tuning & Query Optimization
PostgreSQL Administration & Managed Services
High Availability, Clustering & Replication
PostgreSQL Backup, Recovery & Disaster Planning
PostgreSQL Security, Compliance & Auditing
PostgreSQL for Analytics & Data Warehousing
PostgreSQL on Cloud & Containers
PostgreSQL Extensions & Open-Source Integrations
PostgreSQL for Every Industry
SQL Server MSSQL
MSSQL Consulting
MSSQL Migration Services
MSSQL Optimization & Query Tuning Services
MSSQL Database Administration Services
MSSQL Backup & Recovery Services
MSSQL High Availability & Replication Services
MSSQL Security & Compliance Services
MSSQL Performance Monitoring & Health Checks
MSSQL Solutions by Industry
Aerospike Aerospike
Aerospike Consulting
Aerospike Migration Services
Aerospike Performance Optimization & Tuning
Aerospike Backup & Recovery
Aerospike High Availability
Aerospike Cloud & Hybrid Deployments
Aerospike for Real-Time Applications (AdTech, FinTech, Retail, IoT)
Clickhouse Clickhouse
ClickHouse Consulting
ClickHouse Migration Services
ClickHouse Optimization & Query Tuning
ClickHouse Database Administration
ClickHouse Backup & Recovery
ClickHouse Security & Maintenance
ClickHouse Cloud Services (ClickHouse Cloud, AWS, GCP, Azure)
ClickHouse Solutions by Industry
ClickHouse High Availability & Replication
TiDB TiDB
TiDB Consulting
TiDB Administration & Maintenance
TiDB Security and Privacy Maintenance
TiDB Performance & Query Optimization
TiDB Migration Services
TiDB Backup & Disaster Recovery
TiDB High Availability Solutions
TiDB Solutions by Industry
TiDB Cloud Services
ScyllaDB ScyllaDB
ScyllaDB Consulting
ScyllaDB Administration & Maintenance
ScyllaDB Security and Privacy Maintenance
ScyllaDB Performance & Query Optimization
ScyllaDB Migration Services
ScyllaDB Backup & Disaster Recovery
ScyllaDB High Availability Solutions
ScyllaDB Solutions by Industry
ScyllaDB Cloud Services
DevOps
DevOps DevOps Services
Version Control Version Control
Kubernetes Kubernetes
Infrastructure Infrastructure Management
Web Servers Web Servers
Networking
Networking Networking Services
Basic Basic
Advanced Advanced
MySQL MySQL
MongoDB MongoDB
PostgreSQL PostgreSQL
MSSQL MSSQL
Aerospike Aerospike
Clickhouse Clickhouse
TiDB TiDB
ScyllaDB ScyllaDB
Version Control Version Control
Kubernetes Kubernetes
Infrastructure Infrastructure Management
Web Servers Web Servers
Basic Basic
Advanced Advanced
MySQL Consulting
MySQL Migration Services
MySQL Optimization & Query Tuning
MySQL Database Administration
MySQL Backup & Recovery
MySQL Security & Maintenance
MySQL Cloud Services (AWS RDS, Aurora, Google Cloud SQL, Azure)
MySQL for Ecommerce
MySQL High Availability & Replication
MongoDB Consulting
MongoDB Migration Services
MongoDB Optimization & Query Tuning
MongoDB Database Administration
MongoDB Backup & Recovery
MongoDB Security & Maintenance
MongoDB Cloud (Atlas)
MongoDB Solutions by Industry
MongoDB High Availability & Replication
PostgreSQL Consulting
PostgreSQL Migration & Upgrades
Performance Tuning & Query Optimization
PostgreSQL Administration & Managed Services
High Availability, Clustering & Replication
PostgreSQL Backup, Recovery & Disaster Planning
PostgreSQL Security, Compliance & Auditing
PostgreSQL for Analytics & Data Warehousing
PostgreSQL on Cloud & Containers
PostgreSQL Extensions & Open-Source Integrations
PostgreSQL for Every Industry
MSSQL Consulting
MSSQL Migration Services
MSSQL Optimization & Query Tuning Services
MSSQL Database Administration Services
MSSQL Backup & Recovery Services
MSSQL High Availability & Replication Services
MSSQL Security & Compliance Services
MSSQL Performance Monitoring & Health Checks
MSSQL Solutions by Industry
Aerospike Consulting
Aerospike Migration Services
Aerospike Performance Optimization & Tuning
Aerospike Backup & Recovery
Aerospike High Availability
Aerospike Cloud & Hybrid Deployments
Aerospike for Real-Time Applications (AdTech, FinTech, Retail, IoT)
ClickHouse Consulting
ClickHouse Migration Services
ClickHouse Optimization & Query Tuning
ClickHouse Database Administration
ClickHouse Backup & Recovery
ClickHouse Security & Maintenance
ClickHouse Cloud Services (ClickHouse Cloud, AWS, GCP, Azure)
ClickHouse Solutions by Industry
ClickHouse High Availability & Replication
TiDB Consulting
TiDB Administration & Maintenance
TiDB Security and Privacy Maintenance
TiDB Performance & Query Optimization
TiDB Migration Services
TiDB Backup & Disaster Recovery
TiDB High Availability Solutions
TiDB Solutions by Industry
TiDB Cloud Services
ScyllaDB Consulting
ScyllaDB Administration & Maintenance
ScyllaDB Security and Privacy Maintenance
ScyllaDB Performance & Query Optimization
ScyllaDB Migration Services
ScyllaDB Backup & Disaster Recovery
ScyllaDB High Availability Solutions
ScyllaDB Solutions by Industry
ScyllaDB Cloud Services
  1. Home
  2. > Blogs
  3. > PostgreSQL
  4. > PostgreSQL 19: 6 Important New Features and Enhancements

PostgreSQL 19: 6 Important New Features and Enhancements

PostgreSQL 19 introduces significant improvements in database maintenance, replication, query optimization, and performance. This blog explores six important enhancements, including the new REPACK command, restart-free logical replication enablement, sequence synchronization, WAIT FOR LSN, query plan management, and parallel autovacuum.

Jethish November 20, 2026

Table of Contents

  • 1. REPACK and REPACK (CONCURRENTLY)
  • Benefits
  • 2. Logical Replication Without a Server Restart
  • Benefits
  • 3. Logical Replication of Sequences and Improved Publication Control
  • Additional logical replication improvements
  • Benefits
  • 4. WAIT FOR LSN: Read-Your-Writes Consistency on Standby Servers
  • Benefits
  • 5. pg_plan_advice: Better Control Over Query Execution Plans
  • Benefits
  • 6. Parallel Autovacuum and Smarter Autovacuum Prioritization
  • Parallel index vacuuming
  • Smarter autovacuum prioritization
  • Additional autovacuum improvements
  • Benefits
  • Conclusion
  • Official References

Subscribe for email updates

RSS feed
Summarize with AI: ChatGPT Google AI Perplexity Claude Grok

PostgreSQL continues to evolve with every major release, introducing improvements that make database administration more efficient, queries faster, and enterprise workloads more reliable. With the release of PostgreSQL 19 on November 19, 2026, the PostgreSQL Global Development Group has introduced several important enhancements focused on database maintenance, replication, query optimization, and performance.

This release addresses several challenges commonly faced by database administrators, including table bloat, query plan instability, logical replication configuration, sequence synchronization, and replication lag in primary-standby architectures.

Let’s explore six powerful enhancements introduced in PostgreSQL 19 and understand how they can benefit database administrators and developers.

1. REPACK and REPACK (CONCURRENTLY)

Table bloat is a common challenge in PostgreSQL environments, particularly for tables that experience frequent UPDATE and DELETE operations.

Traditionally, PostgreSQL DBAs have relied on VACUUM FULL and CLUSTER to reclaim disk space and reorganize table contents. However, these operations have different purposes and can require strong locks that prevent normal access to the affected table during maintenance.

PostgreSQL 19 introduces the new REPACK command, bringing these table-reorganization capabilities under a unified command. The existing VACUUM FULL and CLUSTER commands remain available for backward compatibility.

The most significant addition is REPACK (CONCURRENTLY). It allows PostgreSQL to rebuild a table without acquiring an access-exclusive lock for the entire operation. This means normal reads and writes can continue while the table is being repacked.

Example:

psql — blogs
-- Rebuild a table without blocking normal reads and writes
blogs=# REPACK (CONCURRENTLY) orders;

DBAs can monitor the operation from another session using the newly introduced pg_stat_progress_repack view.

psql — blogs
-- Monitor table repacking progress
blogs=# SELECT * FROM pg_stat_progress_repack;

PostgreSQL 19 also introduces the max_repack_replication_slots configuration parameter to control the replication slots required for concurrent repacking.

Benefits

  • Enables online table bloat removal without blocking normal reads and writes for the duration of the operation.
  • Combines table-reorganization capabilities into a single command.
  • Provides built-in progress monitoring through pg_stat_progress_repack.
  • Helps DBAs perform table maintenance with less operational disruption.

For a detailed explanation of how REPACK works and how to test it, read our dedicated guide: REPACK in PostgreSQL 19: Finally, Online Table Bloat Removal.

2. Logical Replication Without a Server Restart

Logical replication is widely used in PostgreSQL environments for database migrations, Change Data Capture (CDC), data synchronization, and reporting workloads.

Previously, enabling logical replication required configuring:

postgresql.conf
wal_level = logical

Since wal_level is a startup parameter, changing it required a PostgreSQL server restart. This could become challenging in production environments where database availability is critical.

PostgreSQL 19 simplifies this process. When wal_level is configured as replica, PostgreSQL can automatically enable logical replication when it is required, without requiring a server restart.

To understand the WAL level currently in effect, PostgreSQL 19 introduces the new read-only parameter:

psql — blogs
blogs=# SHOW effective_wal_level;

This provides visibility into the effective WAL level being used by the server.

Benefits

  • Eliminates the need for a server restart solely to enable logical replication when wal_level is set to replica.
  • Simplifies the initial setup of logical replication and CDC pipelines.
  • Reduces operational disruption in production environments.
  • Provides better visibility into the effective WAL configuration.

This enhancement is particularly useful for organizations running logical replication and CDC platforms, where minimizing database restarts is important.

Read our detailed article to understand how this feature works: PostgreSQL 19: A Smarter Way to Enable Logical Decoding with effective_wal_level.

3. Logical Replication of Sequences and Improved Publication Control

Logical replication has traditionally replicated table changes, but sequence values were not automatically synchronized between publishers and subscribers. This created challenges during database migrations and application cutovers, especially when applications depended on sequences to generate unique identifiers.

PostgreSQL 19 addresses this limitation by introducing logical replication support for sequence values. DBAs can now publish all sequences using:

psql — publisher
blogs=# CREATE PUBLICATION pub_all_seq FOR ALL SEQUENCES;

On the subscriber, sequence synchronization can be performed using:

psql — subscriber
blogs=# ALTER SUBSCRIPTION sub_main REFRESH SEQUENCES;

This helps synchronize sequence values between the publisher and subscriber, reducing the manual effort involved in preparing a replicated database for cutover.

Additional logical replication improvements

PostgreSQL 19 also introduces several improvements to publication and subscription management.

  • Excluding tables from publications: the new EXCEPT clause allows DBAs to exclude specific tables when publishing all tables. This is useful when most tables need to be replicated but certain tables should remain excluded.
  • Retaining deleted tuple information: the new retain_dead_tuples subscription option retains information required for certain replication conflict detection scenarios. The max_retention_duration setting can be used to limit how long this information is retained.
  • Improved sequence synchronization monitoring: the pg_stat_subscription_stats view introduces the sync_seq_error_count column to track sequence synchronization errors separately.

Benefits

  • Synchronizes sequence values between publishers and subscribers.
  • Reduces manual sequence adjustments during database migrations and cutovers.
  • Provides greater flexibility when managing publication membership.
  • Improves visibility into sequence synchronization errors.

These improvements make PostgreSQL logical replication more suitable for migration and CDC use cases where sequence consistency is important.

Need expert guidance on PostgreSQL 19? Connect with Mafiree’s PostgreSQL experts today!

Talk to Our PostgreSQL Experts

4. WAIT FOR LSN: Read-Your-Writes Consistency on Standby Servers

In PostgreSQL streaming replication environments, read queries are often routed to standby servers to distribute workloads and reduce pressure on the primary server. However, asynchronous replication introduces a familiar challenge: replication lag.

When an application performs a write on the primary and immediately reads the same record from a standby, the latest transaction may not yet have been replayed. This can result in stale data being returned to the application.

PostgreSQL 19 introduces the new WAIT command to address this challenge. Using WAIT FOR LSN, a session connected to a standby server can wait until the standby has reached a specified WAL position before executing subsequent queries.

Example:

psql — standby
blogs=# WAIT FOR LSN '0/0306EE20';

By default, this command waits until the specified LSN has been replayed on the standby server. Once the target LSN is reached, the application can execute its read query with the assurance that the corresponding WAL changes have been replayed.

PostgreSQL 19 also supports different waiting modes:

  • standby_replay – Waits until the WAL has been replayed on the standby.
  • standby_write – Waits until the WAL has been written to the operating system.
  • standby_flush – Waits until the WAL has been flushed to durable storage on the standby.
  • primary_flush – Waits until the WAL has been flushed on the primary server.

A timeout can also be specified to prevent an application from waiting indefinitely.

Example with timeout:

psql — standby
blogs=# WAIT FOR LSN '0/0306EE20'
blogs-# WITH (
blogs(#   MODE 'standby_replay',
blogs(#   TIMEOUT '5s',
blogs(#   NO_THROW
blogs(# );

Benefits

  • Helps applications achieve read-your-writes consistency.
  • Reduces the possibility of reading stale data immediately after a write.
  • Improves consistency when applications use asynchronous replicas for read scaling.
  • Provides flexibility through different WAL waiting modes and timeout options.

For applications using HAProxy, PgBouncer, or application-level read/write routing, this is an important enhancement.

Important consideration: the application must capture the relevant LSN from the primary after the write transaction commits and pass it to the standby session. The WAIT command must also execute before the session takes locks or acquires a snapshot that could interfere with WAL replay.

5. pg_plan_advice: Better Control Over Query Execution Plans

Query plan instability is a familiar challenge for PostgreSQL DBAs. A query that performs efficiently today may become slower tomorrow because of changes in data distribution, statistics, or query planner decisions.

Traditionally, DBAs have used techniques such as query rewriting, indexing, statistics adjustments, and configuration tuning to address these issues.

PostgreSQL 19 introduces the pg_plan_advice extension, which provides better control over query planner decisions. It allows DBAs to provide plan advice and experiment with alternative execution plans using a dedicated plan-advice language. This helps stabilize query plans without necessarily modifying the application’s SQL statements.

PostgreSQL 19 also introduces the companion pg_stash_advice extension. It stores plan advice and automatically applies it to queries based on their query identifiers. This is particularly useful when a critical application query starts choosing a less efficient execution plan after changes in data volume or distribution.

Benefits

  • Provides greater control over query planner decisions.
  • Helps stabilize execution plans for critical queries.
  • Reduces the need to modify application SQL statements.
  • Helps address unexpected query performance degradation.
  • Makes it easier to experiment with alternative execution plans.

For DBAs managing high-volume transactional systems, this feature provides another approach to maintaining predictable query performance.

6. Parallel Autovacuum and Smarter Autovacuum Prioritization

Autovacuum is one of the most important background processes in PostgreSQL. It is responsible for reclaiming dead tuples, updating statistics, maintaining visibility information, and preventing transaction ID wraparound.

However, in databases containing large tables and multiple indexes, vacuum operations can take considerable time and consume significant system resources. PostgreSQL 19 introduces improvements to make autovacuum more efficient.

Parallel index vacuuming

PostgreSQL 19 allows autovacuum to use parallel workers when processing table indexes. The maximum number of workers is controlled by the new server configuration parameter:

postgresql.conf
autovacuum_max_parallel_workers = 4

DBAs can also configure the number of parallel autovacuum workers for individual tables using the autovacuum_parallel_workers storage parameter.

psql — blogs
blogs=# ALTER TABLE orders SET (autovacuum_parallel_workers = 4);

This allows large tables with multiple indexes to benefit from parallel index vacuuming, potentially reducing maintenance time.

Smarter autovacuum prioritization

Another important enhancement is the introduction of a scoring-based prioritization system. Previously, autovacuum primarily relied on thresholds and eligibility conditions to determine which tables required maintenance. PostgreSQL 19 introduces a scoring mechanism to determine the order in which eligible tables should be processed.

The scoring system considers factors such as:

  • Transaction ID freeze requirements.
  • Multixact freeze requirements.
  • Dead tuple accumulation.
  • Insert activity.
  • Analyze requirements.

DBAs can tune the scoring weights using new configuration parameters:

  • autovacuum_freeze_score_weight
  • autovacuum_multixact_freeze_score_weight
  • autovacuum_vacuum_score_weight
  • autovacuum_vacuum_insert_score_weight
  • autovacuum_analyze_score_weight

The new pg_stat_autovacuum_scores view provides visibility into the per-table autovacuum prioritization details.

psql — blogs
-- Inspect autovacuum prioritization
blogs=# SELECT * FROM pg_stat_autovacuum_scores;

Additional autovacuum improvements

PostgreSQL 19 also introduces several monitoring and maintenance improvements:

  • pg_stat_progress_vacuum now includes started_by and mode columns to identify who initiated the vacuum and its aggressiveness.
  • The new log_autoanalyze_min_duration parameter allows DBAs to log long-running autovacuum analyze operations separately.
  • Transaction ID and multixact wraparound warnings now begin when fewer than 100 million transactions remain, compared with the previous threshold of 40 million.
  • Queries scanning table pages can now mark eligible pages as all-visible in the visibility map, potentially reducing work during future vacuum operations.

Benefits

  • Enables parallel index maintenance for eligible autovacuum operations.
  • Helps prioritize tables that require maintenance.
  • Provides better visibility into autovacuum decisions and progress.
  • Improves monitoring of vacuum and analyze operations.
  • Helps DBAs manage large, high-transaction databases more effectively.

For a deeper understanding of autovacuum behavior, thresholds, and configuration, read our guide: PostgreSQL Autovacuum Explained in Detail.

For assistance with PostgreSQL major version upgrades and migration planning, explore Mafiree’s PostgreSQL Migration and Upgrade Services.

Conclusion

PostgreSQL 19 introduces meaningful improvements across database maintenance, replication, query optimization, and performance management. Features such as REPACK (CONCURRENTLY), restart-free logical replication enablement, sequence synchronization, WAIT FOR LSN, and smarter autovacuum provide practical solutions to challenges faced by database administrators in production environments.

For DBAs, these enhancements offer better control over maintenance operations, replication consistency, and query execution. For developers, they introduce capabilities that simplify application development and data synchronization.

As PostgreSQL continues to evolve, understanding these changes will help organizations make informed decisions about database performance, scalability, reliability, and future upgrades.

At Mafiree, we continue to explore PostgreSQL innovations and help organizations build, manage, optimize, and scale reliable database environments.

Official References

  • PostgreSQL 19 Release Notes: https://www.postgresql.org/docs/19/release-19.html

FAQ

Many DBAs will point to REPACK (CONCURRENTLY), which removes table bloat online, along with parallel autovacuum and the planner advice modules.
Yes. With wal_level = replica, logical replication can be enabled automatically when needed, and effective_wal_level shows the active level.
Use pg_upgrade, a dump/restore with pg_dumpall, or logical replication. Test in staging first, because several defaults changed.
WAIT FOR LSN is part of the new WAIT command. It allows a session on a standby server to wait until a specified WAL position has been written, flushed, or replayed. The default mode waits for replay, helping applications achieve read-your-writes consistency.
PostgreSQL 19 is a stable major release. However, organizations should validate application compatibility, extension support, backup and recovery procedures, replication behavior, and workload performance before deploying it in production.
PostgreSQL 19 introduces several enhancements, including the REPACK command, concurrent table repacking, restart-free logical replication enablement, sequence replication, the WAIT FOR LSN capability, the pg_plan_advice extension, and parallel autovacuum.

Author Bio

Jethish

Jethish is a PostgreSQL DBA at Mafiree with expertise in building scalable, reliable, and high-performance database infrastructures. He focuses on PostgreSQL architecture, replication strategies, performance tuning, and high availability for mission-critical systems. Through his technical writing, he shares clear, practical insights on database internals, replication choices, load balancing, and cross-database integrations that help engineers and DBAs tackle real-world data challenges.

Leave a Comment

Related Blogs

PostgreSQL 19: A Smarter Way to Enable Logical Decoding with effective_wal_level

PostgreSQL 19 introduces effective_wal_level, allowing logical decoding to be enabled dynamically when required, without changing wal_level or restarting the PostgreSQL server.

  792 views
PostgreSQL Indexing: B-Tree, GIN, BRIN and When Each One Actually Helps

Learn how to choose the right PostgreSQL index for better query performance. This guide explains B-Tree, GIN, and BRIN indexes, their ideal use cases, performance characteristics, and key indexing best practices to help optimize PostgreSQL databases efficiently.

  643 views
PostgreSQL Replication Setup: Step-by-Step Guide for Streaming Replication and Failover

Understand how PostgreSQL streaming replication works, deploy a primary server and replica node, implement failover for high availability, and optimize your replication setup with Mafiree's expert DBA services. Ensuring high availability and data protection in PostgreSQL environments is critical for modern applications. One of the most effective ways to achieve this is through PostgreSQL replication setup, particularly using streaming replication with failover capabilities. This guide walks you through configuring a robust PostgreSQL replication system, covering everything from basic setup to handling failover scenarios.

  688 views
REPACK in PostgreSQL 19: Finally, Online Table Bloat Removal in Core

PostgreSQL 19 introduces REPACK, a native command that unifies the functionality of VACUUM FULL and CLUSTER while adding support for CONCURRENTLY to minimize downtime. Unlike traditional table rewrites that require long ACCESS EXCLUSIVE locks, REPACK can reclaim table bloat online by copying live data, rebuilding indexes, and applying concurrent changes before a final metadata swap. This article explores how REPACK works internally, compares it with VACUUM FULL and pg_repack, demonstrates a hands-on performance test, explains the new pg_stat_progress_repack monitoring view, and covers current limitations and best practices for production environments.

  13939 views
ProxySQL vs HAProxy for MySQL High Availability: Complete Comparison 2026

ProxySQL excels in MySQL-specific query routing, read/write splitting, and performance tuning. HAProxy offers robust load balancing across multiple protocols and is ideal for general-purpose proxying. Choose ProxySQL if your focus is on MySQL optimization; select HAProxy for broader application-level load balancing. Both tools support failover mechanisms but with different levels of database-specific integration.

  825 views
Tracking PostgreSQL Operations in Real Time: A Deep Dive into PostgreSQL Progress Reporting

This blog explores PostgreSQL’s progress reporting system views that provide real-time visibility into long-running operations like VACUUM, ANALYZE, CREATE INDEX, COPY, and base backups. It explains how DBAs can monitor execution phases, estimate completion, detect bottlenecks, and improve operational efficiency using these built-in views. Real-world examples and use cases demonstrate how progress tracking enhances performance tuning, automation, and maintenance planning.

  13741 views
Key Differences Between MySQL and PostgreSQL: Architecture, Performance & Use Cases

Understanding the difference between MySQL and PostgreSQL is critical when choosing a database for production workloads. While both are powerful open-source relational databases, they are built with fundamentally different philosophies. This comprehensive guide compares MySQL vs PostgreSQL across architecture, performance behavior under concurrent loads, replication strategies, and real-world use cases — backed by Mafiree's 17+ years of hands-on production experience across India, APAC, and the Middle East.

  1722 views
AWS Database Storage Optimization: How We Reclaimed 3.6 TB and Cut Costs in Half

A client came to us with a classic AWS database storage optimization problem: 15.2 TB allocated, less than a third actually in use — and a bill that kept growing regardless. Within one week, Mafiree had reclaimed 3.6 TB, validated a safe path to cut allocation nearly in half, and executed a zero-downtime migration. Here's the full story.

  1253 views
PostgreSQL Connection Pooling: PgBouncer vs Odyssey – Performance & Configuration

PostgreSQL uses a process-per-connection model, which can limit scalability in high-traffic environments. Connection poolers help manage this challenge by reusing database connections efficiently. This blog compares PgBouncer and Odyssey, two popular PostgreSQL connection poolers, highlighting their architecture, performance characteristics, configuration differences, and ideal use cases. It helps organizations choose the right pooling solution based on workload scale, complexity, and operational requirements.

  8335 views
8 Enhancing Features in PostgreSQL 18

PostgreSQL 18: Efficiency, security, and reliability, all in one upgrade

  13495 views
Optimizing PostgreSQL Queries with Functional Indexes – A Real-World Case Study

Cutting Query Time from 10 Minutes to Under 1 Second – How Functional Indexes Helped Us Optimize Aurora PostgreSQL and Stabilize CPU Performance.

  4965 views
Mastering PostgreSQL Meta-Commands: The Ultimate psql Cheat Sheet

Why memorize SQL queries when \d, \l, and \dx do the heavy lifting? Learn the power of PostgreSQL’s psql meta-commands today.

  5853 views
Choosing the Right Replication Type in PostgreSQL

Choosing the Right Replication Type in PostgreSQL – Understand the key differences between Streaming and Logical Replication, their best use cases, and how to implement them effectively for high availability, scalability, and disaster recovery.

  4473 views
PostgreSQL Schema Changes pg_osc: Zero-Downtime Migrations for Production Systems

Altering large tables in PostgreSQL can cause locks, performance issues, and downtime in production environments. This blog explains how pg_osc (PostgreSQL Online Schema Change) enables safe schema modifications using a shadow table approach, allowing applications to continue operating during migrations. The article covers how pg_osc works, compares it with alternatives like pg_repack, explores real-world use cases, and provides practical steps for implementing online schema changes in production. It also highlights best practices used by Mafiree to perform reliable zero-downtime PostgreSQL schema migrations in high-traffic environments.

  3702 views
Connecting MySQL to PostgreSQL Using mysql_fdw for Cross-DB Queries

This illustration represents the power of mysql_fdw in enabling smooth data exchange and real-time connectivity between MySQL and PostgreSQL. A perfect solution for cross-database operations and data integration!

  5201 views
Incremental Backup In PostgreSQL 17

Revolutionize your database management with PostgreSQL 17! Experience faster, smarter, and more efficient backups with the power of incremental backup. Reduce storage, save time, and ensure seamless recovery – the future of PostgreSQL backup starts here!

  1903 views
A Practical Guide to PostgreSQL Load Balancing

Load balancing in PostgreSQL distributes client connections across multiple database servers to improve performance, scalability, and availability. This guide compares Pgpool-II, ProxySQL, and HAProxy, covering their key features, advantages, limitations, and suitability for PostgreSQL workloads.

  13603 views
7 Enhancing Features In PostgreSQL 17

PostgreSQL 17 is here to revolutionize your database experience! Packed with enhanced performance, cutting-edge features, and improved scalability, this release is designed to meet the evolving demands of modern applications. Whether you're handling complex queries or scaling to new heights, PostgreSQL 17 brings unparalleled reliability and efficiency to your data management solutions.

  4169 views
6 Interesting Features in PostgreSQL 16

Recently Postgres 16 has launched and I have picked the most interesting feature in this blog.

  6032 views
PostgreSQL Autovacuum Explained in Detail

This blog explains how PostgreSQL Autovacuum works — covering the launcher/worker process model, the exact formula that decides when a table becomes eligible, and the key differences between VACUUM, Autovacuum, and VACUUM FULL. It includes an interactive eligibility calculator, tunable parameters, monitoring queries, and best practices to help DBAs prevent table bloat and transaction ID wraparound.

  2256 views

Subscribe for email updates

RSS feed
Get in touch with us

Highlights

More than 6000 Servers Monitored

Happy Clients

Certified DBAs

24 x 7 x 365 Support

PCI

Database Services

MySQL MongoDB PostgreSQL SQL Server Aerospike Clickhouse TiDB ScyllaDB

Quick Links

Careers Blog Contact Privacy Policy Disclaimer Policy

Contacts

Linkedin Mafiree Facebook Mafiree Twitter Mafiree

Nagercoil Office

Miru IT Park, Vallankumaranvillai,

Nagercoil, Tamilnadu - 629 002.

Bangalore Office

Unit 303, Vanguard Rise,

5th Main, Konena Agrahara,

Old Airport Road, Bangalore - 560 017.

Call: +91 6383016411

Email: sales@mafiree.com


Copyright © - All Rights Reserved - Mafiree