Greg Nokes
4 min read
Latest Articles
- Accessing Large Language Models from PostgreSQL
- 8 Steps in Writing Analytical SQL Queries
- 4 Ways to Create Date Bins in Postgres: interval, date_trunc, extract, and to_char
- Crunchy Postgres for Kubernetes 5.7: Faster Backups, Automated Snapshots, Postgres 17 and More
- pg_parquet: An Extension to Connect Postgres and Parquet
Crunchy Postgres for Kubernetes 5.7: Faster Backups, Automated Snapshots, Postgres 17 and More
We are excited to announce the release of Crunchy Postgres for Kubernetes 5.7! This latest version brings a wealth of new features and enhancements designed to make your Postgres deployments on Kubernetes more flexible, efficient, secure, and robust than ever before.
We have highlighted a few of the features that we are excited about below. You can also check out the release notes for more details
Backup Features
We took a close look at our backup and disaster recovery systems to identify areas where we could improve performance and add functionality while continuing to maintain a focus on protecting your data.
Automated Snapshots
Crunchy Postgres for Kubernetes can now manage snapshots of your database. When you enable this feature, we will automatically create and manage snapshots of your database. We will also automatically use and apply them when possible to accelerate clones. We have seen some impressive improvements in clone creation speed. Expect to see more and more instances where we automatically use snapshots to speed up replica creation and restores.
For example, if you were running Crunchy Postgres for Kubernetes on GKE, you could use this stanza to enable snapshots:
spec:
backups:
snapshots:
volumeSnapshotClassName: gke-snapshotclass
Asynchronous Archiving by Default
One of the standout features in 5.7 is the shift to asynchronous archiving by default. This change enhances performance by allowing write-ahead logging (WAL) archiving to occur asynchronously, reducing potential delays in data processing.
With the operator now managing the spool-path, there's also less configuration overhead. If you have previously set the spool-path in your configuration, you can safely remove that setting after upgrading. You can also delete the associated directory, streamlining your setup.
After upgrading, a new log file at pgdata/pgbackrest/log/db-archive-push-async.log
will help you track WAL archiving, providing better insights into your database operations.
Backup from Replicas with pgBackRest
Crunchy Postgres for Kubernetes 5.7 introduces the ability to enable backups from replicas within your pgBackRest configuration. This feature allows you to offload backup operations from the primary instance to replicas, minimizing the impact on your primary database's performance. By ensuring you have at least one Postgres replica available and setting spec.backups.pgbackrest.global.backup-standby: "y"
, you can enhance your backup strategy with ease.
Option to Disable Backups for Specific Clusters
We understand that not all databases require backups, especially in development and testing environments. With 5.7, you can now turn off backups for individual clusters. This capability is particularly useful for ephemeral or short-lived databases where backups might not be necessary. The operator will manage WAL files appropriately, ensuring smooth operation without the overhead of unnecessary backups.
Support for Postgres 17
Staying current with the latest Postgres developments is essential for leveraging new features and performance improvements. Version 5.7 now includes support for Postgres version 17, allowing you to take advantage of and test the latest advancements in the Postgres ecosystem. This update ensures that your deployments are future-proof and optimized for the best performance. We have several posts on Postgres 17 features you might want to take advantage of.
pgAdmin 4 Updates
Security remains a top priority, and version 5.7 of Crunchy Postgres for Kubernetes strengthens this by introducing Kerberos authentication support for pgAdmin 4 deployments created via the PGAdmin API. This integration allows for secure, single sign-on authentication, aligning with enterprise security protocols and continuing to provide the best, most seamless user experience for pgAdmin in Kubernetes.
Upgrade to Crunchy Postgres for Kubernetes 5.7
Crunchy Postgres for Kubernetes 5.7 represents a significant leap forward in Postgres Kubernetes deployments. Our commitment to enhancing performance, security, and ease of management shows in this update. Check out the full release notes for details about all of the changes. By choosing 5.7, you're investing in a solution that grows with your needs, offers unparalleled flexibility, and delivers enterprise-grade features out of the box.
After you update, you will appreciate the seamless integration of new functionalities that enhance existing workflows. Version5.7 offers a comprehensive, competitive edge—delivering robust features that simplify database management on Kubernetes while ensuring high availability and security.
We invite everyone to upgrade to 5.7 and experience the new features firsthand. Upgrading is straightforward. And, if you are exploring Postgres solutions on Kubernetes, there's no better time to discover what Crunchy Postgres for Kubernetes has to offer.
Join the Community
We believe in the power of community and open-source collaboration is in our DNA. Join our Discord community forums to connect with other users, share your experiences, and learn best practices. Your feedback is invaluable in helping us continue to improve and deliver the features that matter most to you.
Related Articles
- Accessing Large Language Models from PostgreSQL
5 min read
- 8 Steps in Writing Analytical SQL Queries
8 min read
- 4 Ways to Create Date Bins in Postgres: interval, date_trunc, extract, and to_char
8 min read
- Crunchy Postgres for Kubernetes 5.7: Faster Backups, Automated Snapshots, Postgres 17 and More
4 min read
- pg_parquet: An Extension to Connect Postgres and Parquet
4 min read