Release 2.1.0 (Autobase)

🚀 Meet Autobase

We’re excited to present the next evolution of our platform — autobase, the powerful automated database platform for PostgreSQL®, now with a fresh name, a new logo, and bold ambitions.

Why autobase? Autobase stands for automated database platform for PostgreSQL®. Our new logo—a cloud icon with arrows pointing up and down—reflects our core value: enabling you to host data effortlessly in the cloud, on-premises, or migrate between environments. Autobase provides full control over your infrastructure—no limits, no compromises.

🎯 DBA as a Service (DBAaaS): We’ve introduced dedicated support packages. Each package includes a PostgreSQL expert (DBA) dedicated to your database cluster, providing personalized assistance and operational expertise.
→ Learn more about support packages here.

🔭 Looking Ahead: Soon, you’ll be able to manage PostgreSQL clusters through an intuitive user interface, simplifying database operations even further. A few examples of what we’re planning for the upcoming releases can be found here and here. These are just initial steps — in future releases, we aim to cover the entire database management lifecycle through the autobase Console (UI).
→ Interested in helping us build this future? Consider becoming a sponsor.

What's Changed

• Possibility of adding privileges to objects by @abyss-ms in #740
• ParadeDB (pg_search, pg_analytics) by @vitabaks in #758
• config_pgcluster: Create extensions after restarting Postgres by @vitabaks in #761
• Add pgvectorscale extension by @vitabaks in #762 #796
• Fix typo in aws_s3_bucket_name variable by @vitabaks in #772
• Login to Azure using Service Principal by @vitabaks in #773
• Install WAL-G from the binary file by @vitabaks in #768
• pg_upgrade.yml: Add ‘string’ filter for postgresql version variables by @ruslanloman in #777
• GCP: Add support for bare metal instances by @vitabaks in #780
• pgBackRest: Run "Create stanza" only on master if it's not posix by @vitabaks in #786
• pgpass: run the task as the root user by @vitabaks in #791
• pg_upgrade.yml: Use pg_old_dir for old psql binaries before upgrade by @vitabaks in #800
• pgBackRest: Point-In-Time Recovery (PITR) Improvements by @vitabaks in #765
• Fix maximum_lag_on_failover case when value set to 0 by @garry-t in #808
• Updated consul config template and parameters to comply with latest version by @garry-t in #806
• Fix: Prevent division by zero in HugePages calculation by @vitabaks in #810
• Ensure retrieval of hugepage size in check mode by @vitabaks in #814
• pgBackRest: Fix timeline divergence after PITR by @SDV109 in #820
• [Rebranding] Rename postgresql_cluster to autobase by @vitabaks in #821
• Add support for PostgreSQL 17 by @vitabaks in #827
• patroni_replication_username in hba by @allig4t0r in #828
• pgBackRest: update configuration file include-path option by @SDV109 in #829
• Add Upgrade Support for Standby Cluster by @vitabaks in #830
• Upgrade: Add PATH for patronictl; Override become_method in Molecule tests by @vitabaks in #832
• Hetzner: Add shared vCPU instance types; EUR -> USD by @nelsonic in #835
• Update vip-manager to v3.0.0; Patroni REST API support by @vitabaks in #840
• Update etcd to v3.5.17 by @vitabaks in #844
• Allow pgvectorscale tasks execution in check_mode by @vitabaks in #846
• Allow WAL-G tasks execution in check_mode by @vitabaks in #847
• automation: Update requirements by @vitabaks in #845
• Release 2.1.0 by @vitabaks in #850

New Contributors

• @ruslanloman made their first contribution in #777
• @allig4t0r made their first contribution in #828
• @nelsonic made their first contribution in #835

Full Changelog: 2.0.0...2.1.0