Lakebase Autoscaling limitations
This feature is in Public Preview in the following regions: us-east-1, us-west-2, eu-west-1.
Lakebase Autoscaling is the new version of Lakebase with autoscaling compute, scale-to-zero, branching, and instant restore. For feature comparison with Lakebase Provisioned, see choosing between versions.
The following limitations apply to Lakebase Postgres Autoscaling.
Lakebase cross-version access
Lakebase Provisioned and Lakebase Autoscaling are separate implementations.
Database instances created in Lakebase Provisioned are not accessible from the Lakebase App, and projects created in the Lakebase App are not accessible from Lakebase Provisioned.
Learn more: Lakebase Postgres
Migration between Lakebase Provisioned and Lakebase Autoscaling
Direct migration between Lakebase Provisioned and Lakebase Autoscaling is not currently supported.
If you need to move data from a Lakebase Provisioned database to a Lakebase Autoscaling database, you can use one of the following methods:
- Reverse ETL: Sync data from Unity Catalog tables into your Lakebase Autoscaling database.
- pg_dump and pg_restore: Export and import data using standard Postgres tools.
Postgres compatibility
Lakebase Postgres Autoscaling supports standard Postgres functionality and is compatible with Postgres 16 and Postgres 17. For detailed information about Postgres feature compatibility and any differences from standard Postgres behavior, see Postgres compatibility.
Feature availability
The following features are not currently supported in Lakebase Autoscaling. These features are available in Lakebase Provisioned.
Core capabilities
High availability (readable secondaries):
Lakebase Autoscaling does not support readable secondaries for high availability. In Lakebase Provisioned, readable secondaries allow high availability nodes to serve read-only workloads using a separate DNS endpoint. See Configure for high availability.
Data integrations
Postgres -> Delta sync:
Direct synchronization from Postgres to Delta tables is not currently supported in Lakebase Autoscaling. This feature is available in Lakebase Provisioned as Private Preview.
Application integrations
Databricks Apps:
- Apps UI integration for resource selection is not supported
- M2M OAuth authentication is not supported
- Apps can connect using standard connection credentials from the Lakebase App UI. See Connection overview.
Feature Store:
Databricks Feature Store integration is not currently supported in Lakebase Autoscaling.
Developer tools
Infrastructure as code:
- Databricks Asset Bundles (DABs) for Lakebase resources
- Terraform provider for Lakebase resources
Programmatic access:
- Lakebase REST API
- Databricks CLI for Lakebase resources
- Databricks SDKs for Lakebase resources
Cost management
Billing tags and budget policies:
- Custom billing tags
- Serverless budget policies
For a complete feature comparison between Lakebase Autoscaling and Lakebase Provisioned, see Feature comparison.