Resize instances

The Crunchy Bridge system supports cluster resizing with minimal downtime and no changes to your connection string. You can change your instance size, storage size, or Postgres major version.

Resizing is a cluster management operation. You can read more about how cluster management is carried out in the overview of cluster management.

Creating a cluster resize

You can create a cluster resize from the cluster overview:

When creating a cluster resize, you can choose to use a different instance size, storage size, and major version. Your original and new monthly costs will appear on the right. You must change one of these parameters of your existing cluster in order to initiate a resize.

If you want to refresh your cluster with the latest Bridge features and Postgres minor version updates but without changing any cluster parameters, you should initiate a cluster refresh instead.

Cluster resize scheduling

Resizes that require a failover will take place during your next maintenance window. If you want to run the resize immediately, click the "Run Upgrade Now" button in cluster settings. If you return to the resize page before a resize failover has begun, you can cancel it. You can read more about maintenance scheduling on the Maintenance docs page.

Resize maintenance details

Increasing storage

When you increase storage without changing the instance size, the platform will attempt to grow the disks on your running cluster, avoiding a failover maintenance operation. The database continues to run while the disks expand and the filesystem is extended to use the new space. Storage increases apply to the primary server as well as any HA standbys.

If the platform cannot complete a disk growth resize (for example, because of limits on how often disks can be modified in a short period), it falls back to the standard failover-based resize process described below.

Other resize operations

When you change the instance size or tier, decrease storage, or change the Postgres major version, Crunchy Bridge will bring up a new machine behind the scenes, copy your data from backups and WAL, and fail over to the new server at the specified time (or during your next maintenance window). You should ensure your application is set up to automatically reconnect to the database since there will be a brief service interruption (estimated to be no more than a few minutes).

The cluster management page has additional details about how cluster resizes operate behind the scenes and what you can expect when you schedule one.