Changelog
The following are recent changes in the Crunchy Bridge product. Each is marked as to whether it applies to a core Postgres feature, a UI change in the Crunchy dashboard, an update to our docs, an update to the Crunchy CLI (command line interface), or a change to the platform’s REST API.
Current
Postgres 14 is now default, again
Now that Postgres 14.4 which addresses a major bug in Postgres' INDEX and REINDEX CONCURRENTLY commands has been available for some time and showing good results, Postgres 14 is once again the default version provisioned with new Bridge clusters.
Signed access tokens
Access tokens are now ephemeral signed objects rather than records persisted to the database. Procuring and authenticating with them stays identical to before.
A side effect of signing is that access tokens are now longer. For best results, continue treating an access token's secret as an opaque string that may be of variable length.
Since procuring an access token is now cheaper in terms of database load, we've removed the rate limit on creating them.
Postgres 14.4 is now available
Postgres 14.4 is now available, and the default for Postgres 14 provisions
We recommend upgrading immediately as 14.4 contains a fix for the upstream bug in Postgres' INDEX and REINDEX CONCURRENTLY
Postgres 13 is temporarily default
We've temporarily changed our default version of Postgres back to 13 while an upstream bug in Postgres' INDEX and REINDEX CONCURRENTLY is being investigated. Users can still create Postgres 14 clusters, but should make sure not to use concurrent index creation or rebuilding.
The Bridge upgrade system provides an easy way to upgrade between major Postgres versions, so you can also create a Postgres 13 cluster today and migrate it to 14 after a bug fix is released.
Postgres 13 is temporarily default
We've temporarily changed our default version of Postgres back to 13 while an upstream bug in Postgres' INDEX and REINDEX CONCURRENTLY is being investigated. Users can still create Postgres 14 clusters, but should make sure not to use concurrent index creation or rebuilding.
The Bridge upgrade system provides an easy way to upgrade between major Postgres versions, so you can also create a Postgres 13 cluster today and migrate it to 14 after a bug fix is released.
Bridge CLI v2.1.0 release
The bridge CLI tool (cb) v2.1.0 has been released.
See official release for more information.
Suspend and resume GCP clusters from the API
The API endpoints that support suspending a cluster and resuming a cluster now support GCP.
Suspended clusters have no active virtual machine (and are therefore unreachable), but their disks are kept so that they can be later unsuspended.
These actions are also available in cb v2.1.0.
Create forks from backups
When viewing the backup list you will be able to create a new fork from any of your backups using the "Fork From Backup" button on that row.
Suspend and resume clusters from the API
New API endpoints are available for suspending a cluster and resuming a cluster. A cluster's current suspended status is available via the is_suspended property on the cluster resource.
Suspended clusters have no active virtual machine (and are therefore unreachable), but their disks are kept so that they can be later unsuspended.
Currently, suspend/resume is only available on AWS and Azure.
These actions are also available in cb v2.1.0.
List and start backups from the API
New API endpoints are available for listing cluster backups and manually starting a cluster backup.
These actions are also available in cb v2.1.0.
h3 extension now available
The h3 extension which adds h3 bindings to Postgres is now available. New instances can enable it with CREATE EXTENSION. Pre-existing instances require a failover to begin using it.
orafce extension now available
The orafce extension which adds provides Oracle compatability functions is now available. New instances can enable it with CREATE EXTENSION. Pre-existing instances require a failover to begin using it.
h3 extension now available
The h3 extension which adds h3 bindings to Postgres is now available. New instances can enable it with CREATE EXTENSION. Pre-existing instances require a failover to begin using it.
Backup listing now available
You can now view the times of your backups and backup history. To shorten fork recovery time you can provision your forks closer to a backup completion to minimize WAL replay.
Add list cluster backups
Added an API endpoint to support listing the current backups for a cluster.
Bridge CLI v2.0.0 release
The bridge CLI tool (cb) v2.0.0 has been released.
See official release for more information.
Postgres 14.3 and Postgres 13.7 is now available
Postgres 14.4 and Postgres 13.7 is now available.
For full release notes on fixes included please review the PostgreSQL release notes.
Bridge CLI v1.3.0 release
The bridge CLI tool (cb) v1.3.0 has been released.
See official release for more information.
Add invoice notes
It is now possible to add a top level note that when set will automatically be applied to all future team invoices.
This top level note is editable from the team invoices page. It is also possible to edit the individual invoice note directly on each invoice.
Bridge CLI v1.2.0 release
The bridge cli tool (cb) v1.2.0 has been released.
See official release for more information.
Container Apps
Container Apps allow you to launch and run a container from directly within Postgres. This feature is currently in public beta.
See container apps for more information.
Add SSL Certificate download for team
Team admins may now download the public certificate used by the Postgres server for encrypting connections with SSL from the settings pages in the Bridge Admin.
Enforce team single sign-on (SSO)
Team admins may now enforce SSO on teams. Find the setting in Team › Settings in Bridge. Admins must be signed in through SSO to activate the enforce SSO feature.
team_member.roles removed
The API has removed the deprecated roles field from team_member. Use of role field is now the only supported method for interacting with a team members role on a team.
team_member.* events generated
The API now generates team_member.* events whenever an account is added, removed, or had its role updated on a team. These are also visible under a team's Audit Log in Dashboard.
Select replicas for support tickets
Users may now select a replica to report when creating a ticket on the Crunchy Bridge Support page. This cuts down on extra message cycles with customers to point our support team to an issue with a replica.
Automatic resizes and low disk notifications
Disks on clusters that reach 90% utilization will be resized automatically to prevent potential operational problems. Disks under 1 TB will increase in size by 25% and disks over 1 TB will increase in size by 10%.
A notice will be sent to a cluster's team's administrators when an automatic resize occurs, and also as a cluster gets closer to being fully – at 75%, 80%, and 85%.
See automatic disk resizes for more information.
Postgres 14.2 and Postgres 13.6 is now available
Postgres 14.4 and Postgres 13.7 is now available.
For full release notes on fixes included please review the PostgreSQL release notes.
Edit team member roles
Team roles can now be changed directly in the Dashboard without the need to remove/add an account to adjust their role.
New database roles
Postgres superuser role, application role, and individual roles are now displayed in the Dashboard. For more detail on the specific roles see the docs for roles API endpoints. Members see only their individual role, while admins and managers see all roles.
Team member get API endpoint
Added an API endpoint to retrieve a specific team member given a team and account ID. See get team member.
Cluster roles API
Added an API to create and manage cluster roles (see cluster roles), including an idempotent endpoint that allows account-specific roles to be easily created.
A new application role also becomes available by default, meant to be useful so that there's an easily-accessible non-superuser role for use in apps connecting to a Bridge cluster.
Detach replicas in Dashboard
Replicas associated with a cluster may now be detached from a cluster in the Replicas section in its Cluster Overview page. Once detached, the replica now behaves as a main cluster and no longer receives updates from the parent. It may take up to a minute before a detached replica is fully ready. After detaching, it may be helpful to rename the cluster in its Settings page to make it more easily distinguishable as a separate cluster.
Generated API reference
The API reference documentation is now generated automatically, making it much more complete, much more accurate, and adding new features like field-specific documentation and request/response examples. Its design has also been iterated, making it more legible, and adding extra visual features like syntax highlighting.
The reference is generated from an OpenAPI specification which is itself generated from the API's own source code, and a periodic job regenerates it from the latest deployed version, so it's no longer easily possible for the reference to drift out of date.
Product changelog
We've added a changelog that highlights new features in the core database product, Dashboard, API, CLI, and documentation. Like Postgres' WAL, the changelog will endeavor to be a durable and robust system for keeping up-to-date with changes as they happen.
Docs redesign
We've redesigned our documentation subsite for better legibility and to make navigation easier. Check it out at docs.crunchybridge.com. We'll continue to iterate on the redesign over the coming months to provide more useful information and refine what's already there.
Restart instance
The Crunchy Bridge Dashboard now supports the ability to restart your Postgres instance. Restart is available within the settings for the cluster.
Postgres 14 is now default
With Postgres 14.1 now released and Postgres 14 having been GA since late September, we've made it the default major version for newly created clusters.
Postgres 14 is now default
With Postgres 14.1 now released and Postgres 14 having been GA since late September, we've made it the default major version for newly created clusters.
Default Postgres major version
The API endpoint to create a cluster at POST /clusters will now default to a Postgres major version instead of requiring one to be specified. Currently this default is Postgres 13, but will change over time as new Postgres versions are released and become sufficiently stable.
Dark mode
The Crunchy Bridge Dashboard now supports dark mode. It can be activated by visiting your account settings.
2021
Replica detach endpoint
Added new API endpoint PUT /clusters/:id/detach which stops replication to a replica, causing the replica become a new primary. Detach is not synchronous, but will take place soon after the API endpoint is invoked.
Server restart endpoint
Added new API endpoint PUT /clusters/:id/restart which restarts a cluster's underlying server. Restart is not synchronous, but will take place soon after the API endpoint is invoked.
Changelog API
Adds new API endpoints GET /changelogs and GET /changelogs/:id which list and get API and feature changes within the Crunchy Bridge product.
Cross platform replica provisioning
Added support for replicas to be provisioned cross platform in Dashboard console. For example, it's now possible to provision a replica in Azure for a primary located in AWS.
Support replica resizing
Added support for replicas to be resized from the Dashboard, available within the replica detail view of the cluster overview.
Error page enhancements
The Crunchy Bridge Dashboard now has a new error page for 404s that provides more helpful cross links and resources.
Postgres 14.1 and Postgres 13.5 is now available
Postgres 14.1 and Postgres 13.5 is now available.
For full release notes on fixes included please review the PostgreSQL release notes.