Lakebase Autoscaling Beta limitations

Beta

Lakebase Postgres (Autoscaling Beta) is the next version of Lakebase, available for evaluation only. For production workloads, use Lakebase Public Preview. See choosing between versions to understand which version is right for you.

The following limitations apply to the Lakebase Postgres Autoscaling Beta.

Lakebase cross-version access

Lakebase Public Preview and Lakebase Autoscaling Beta are separate implementations with different feature sets:

• Lakebase Public Preview uses database instances to organize database resources.
• Lakebase Autoscaling Beta uses database projects and introduces enhanced capabilities including autoscaling, database branching, scale-to-zero, and instant restore.

Database instances created in the Lakebase Public Preview are not accessible from the Lakebase App, and database projects created in the Lakebase App are not accessible from the Lakebase Public Preview version.

Learn more: Lakebase Postgres

Migration between Lakebase Public Preview and Autoscaling Beta

Direct migration between Lakebase Public Preview and Autoscaling Beta is not currently supported.

If you need to move data from a Lakebase Public Preview database to a Lakebase Autoscaling Beta database, you can use one of the following methods:

• Reverse ETL: Sync data from Unity Catalog tables into your Lakebase Autoscaling Beta database
• pg_dump and pg_restore: Export and import data using standard Postgres tools

Postgres compatibility

Lakebase Postgres (Autoscaling Beta) 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.

High availability

Lakebase Autoscaling Beta does not yet support readable secondaries for high availability. This feature is only available in the Lakebase Public Preview version.

In Lakebase Public Preview, readable secondaries allow high availability nodes to serve read-only workloads using a separate DNS endpoint. See Configure for high availability for more information about this feature in the Public Preview version.

Databricks platform integrations

The following Databricks platform features and integrations are not supported in the Beta release:

Application and data integrations:

• Databricks Apps integration
• Databricks Feature Store integration
• Databricks Notebooks
• Databricks SQL Editor

Access control:

• Workspace access control lists (ACLs) for database project permissions

Infrastructure as code:

• Databricks Asset Bundles (DABs)
• Terraform provider for Lakebase resources

Cost management:

• Billing tags (custom tags)
• Serverless budget policies

APIs and programmatic access:

• Lakebase REST API
• Databricks CLI for Lakebase resources
• Databricks SDKs for Lakebase resources

These features are currently only supported with the Lakebase Public Preview version. See Database instances.