Cluster storage configuration
You can configure storage settings for network-attached storage PlanetScale for Postgres clusters in the "Storage" tab on the Cluster configuration page for your database.
Note
For PlanetScale for Postgres clusters launched on PlanetScale Metal instances, storage is scaled by directly scaling the cluster instance size. Storage autoscaling is not available for Metal clusters. To learn more see the documentation for PlanetScale Metal.
Configuring storage settings
You must be a database or organization administrator to modify these settings.
- From the PlanetScale organization dashboard, select the desired database
- Navigate to the Cluster configuration page from the menu on the left
- Choose the branch whose storage settings you'd like to configure in the "Branch" dropdown
- Select the Storage tab
- Configure your disk size and autoscaling settings
- Set your storage limit as needed
- Click "Queue storage changes"
- Once you're ready to apply the changes, click "Apply changes"
Disk configuration
Disk size
Configure the minimum disk size for your database cluster. This setting determines the initial storage capacity allocated to your database. The disk size is specified in GB and serves as the baseline storage allocation for your cluster.
Note
The maximum disk size for network attached storage is 16384 GB (16 TiB).Enable autoscaling
Note
PlanetScale storage autoscaling is only for network-attached storage database clusters. For PlanetScale Metal based clusters you will need to increase the cluster instance size.
When enabled, autoscaling automatically increases storage when your database approaches a disk size utilization threshold, preventing storage-related outages without manual intervention.
Autoscaling will grow the cluster's storage without you needing to make any configuration changes or updates to the configuration of the database cluster. The new additional space will become available as soon as the scaling action has completed.
Autoscaling thresholds and behaviors
Disk size utilization thresholds
| Volume size | % used |
|---|---|
| < 4 TiB | 70% |
| > 4 TiB | 90% |
Key behaviors of PlanetScale's storage autoscaling:
- Cluster storage can only scale once in a 6 hour period
- Cluster storage scales proportionally based on current size
- Smaller disks receive larger percentage increases, while larger disks receive smaller percentage increases
- All disks grow by a minimum of 50% when autoscaling occurs
- If you need to scale cluster storage by more than 200% within 24 hours, manually scale disk size ahead of time
- Autoscaling will not scale past your configured Storage limit
Storage limit
The storage limit sets the maximum amount of storage that can be allocated to your database cluster through autoscaling. This acts as a ceiling to prevent unlimited storage growth and helps control costs.
When autoscaling is enabled, your storage can grow from the minimum disk size up to the storage limit you specify. The storage limit should be set higher than your initial disk size to allow for growth while providing a reasonable upper bound for your storage costs.
Note
The maximum disk size for network attached storage is 16384 GB (16 TiB).
Tracking changes to storage settings
You can click on the "Changes" tab on the Cluster configuration page to view a log of any changes made to your storage settings. The log will include the settings affected, the original and updated values, status, user that made the changes, start time, and end time.
Need help?
Get help from the PlanetScale Support team, or join our GitHub discussion board to see how others are using PlanetScale.