In this blog post, you’ll first get a glimpse into some of our favorite features in Postgres 14. These include connection scaling, faster VACUUM, and improvements to crash recovery times. By Ozgun Erdogan.
With each new PostgreSQL release, there can be breaking changes with any of the above integration points. The process of making extensions compatible with Postgres versions is incorporating changes to these integration points. For example, with PostgreSQL 14, the utility hook’s signature changed to include a new argument. So, we had to incorporate this change, as shown below. You can also read the complete set of changes for Postgres 14 integration in this pull request.
The article the reads about:
- Favorite new features in PostgreSQL 14
- Making Citus & other extensions compatible with PostgreSQL 14
- Hyperscale (Citus) – Releasing a new PostgreSQL version
The first best practice is the separation of responsibilities between Hyperscale (Citus)’s control plane and data plane. In our architecture, the control plane is responsible for the business logic for managing Postgres/Citus databases. This logic includes periodic health checks, high availability and failover, backup and restore, read replicas, regular maintenance operations, and others. The data plane is solely responsible for running the database. As such, the data plane contains almost nothing else other than stock PostgreSQL and its extensions.
In summary, authors were excited to announce general availability (GA) for Postgres 14 on Azure, within one day of the official Postgres 14 release. Good read!
[Read More]