PostgreSQL 16 Released

PostgreSQL 16 Released

After 11 months of development, the new stable branch of the DBMS PostgreSQL 16 has been published. Updates for the new branch will be available for the next five years until November 2028. Support for PostgreSQL 11.x, the oldest supported branch, will be discontinued on November 9th.

Basic Innovations

  • Mechanism logical replication has been expanded to allow broadcasting changes made in the database during the addition, removal, or updating of records to another server. This includes replicating changes from the reserve server (Standby). This means that operations such as “Insert”, “Update”, and “Delete” can be performed on the backup server and replicated to other servers. For example, in situations of high load on the primary user server, switching to a backup server that replicates changes to the rest of the servers becomes possible.
  • Support for double-destroyed logical replication of tables has been added, allowing the synchronization of changes in two tables on different servers. PostgreSQL 16 also enables the creation of configurations with several active servers using the “Active-CTI” mode.
  • Logical replication productivity has been increased. Notable improvements include the ability to use parallel to handlers when using large transactions subscribers. Additionally, B-Tree indices can now be used for tables without primary keys on the subscriber side, eliminating the need for consistent scanning when searching for records. The initial synchronization of some tables in binary format has also been accelerated.
  • Means of managing access to logical replication have been expanded. For instance, the new predetermined role “pg_create_subscription” allows users to create new subscriptions.
  • Support has been added for customer clients using the Libpq regular library. This includes load balancing, allowing the client to connect to different hosts in a certain or random order. If a host is not available, the client attempts to connect to another server. Once the connection is established, requests within the session are sent to the selected server.
  • The request planner has been optimized and improved. Some of the enhancements include the ability to dispose of the service operations of tables “
/Reports, release notes, official announcements.