PostgreSQL 18: Part 2 or CommitFest 2024-09

September’s CommitFest typically sees a decline in activity, but the recent version 18 CommitFest has proven to be an exception, showcasing a wealth of accepted patches and exciting new features. For those who may have missed the July CommitFest, a recap can be found here.

New Features and Enhancements

Among the noteworthy contributions are:

One of the standout features is the conflict detection and logging in logical replication. This enhancement addresses the challenges posed by independent data changes on subscribers and publishers, which can lead to logical replication conflicts. The new logging tools provide visibility into these conflicts, allowing developers to monitor and manage them effectively.

Another significant update is the Planner: no more 10000000000, which removes the prohibitive constant that inflated the cost of sequential scans. This change allows the planner to make more informed decisions without artificial cost inflation, enhancing query performance.

In addition, improvements in memory management and usage monitoring for temporary tuple storage have been introduced. This update optimizes how temporary tuples are stored, leading to better performance and resource management.

Furthermore, the pg_upgrade tool now supports asynchronous operations across multiple databases, significantly speeding up the upgrade process. This enhancement, along with various performance optimizations for hash joins and numeric operations, demonstrates a commitment to improving the efficiency of PostgreSQL.

As the community continues to innovate, the latest features and enhancements from the CommitFest promise to elevate the PostgreSQL experience for developers and users alike.

Tech Optimizer
PostgreSQL 18: Part 2 or CommitFest 2024-09