Change Intelligence is coming.

Get a First Look

What Lakebase (Databricks Postgres) features does Liquibase support?

Last updated: July 24, 2026

Lakebase (Databricks Postgres) is a fully managed PostgreSQL-compatible database service built on Databricks serverless compute. It exposes a standard PostgreSQL endpoint at jdbc:postgresql://<instance-id>.database.cloud.databricks.com:5432/databricks_postgres, enabling connections using the standard PostgreSQL JDBC driver.

You can use most standard Liquibase Change Types with Lakebase. No dedicated Liquibase extension is required. Lakebase uses the standard PostgreSQL JDBC driver.

Liquibase Community supports Lakebase using the standard PostgreSQL JDBC driver. Liquibase Secure users can access additional Secure-specific Change Types and features such as Composite Types, Triggers, Functions, and Constraints. For more information, see What Lakebase (Databricks Postgres) features does Liquibase Secure support?

To learn how to install, configure, and use Liquibase with your Lakebase instance, see Connect Liquibase with Lakebase.

Features

Supported Change Types

Lakebase behaves as standard PostgreSQL from a Liquibase perspective. There are no Lakebase-specific Change Types, and no dedicated Liquibase extension is required.

Change Type

Limitations

addAutoIncrement

addColumn

addDefaultValue

addDefaultValueBoolean

addDefaultValueComputed

addDefaultValueDate

addDefaultValueNumeric

addDefaultValueSequenceNext

addForeignKeyConstraint

addLookupTable

addNotNullConstraint

addPrimaryKey

addUniqueConstraint

alterSequence

createIndex

createMaterializedView

Use a <sql> changeset with raw CREATE MATERIALIZED VIEW SQL. The <createView materialized="true"> attribute is not supported in the current Liquibase XSD.

createProcedure

Requires splitStatements="false" for PL/pgSQL dollar-quoted ($) bodies.

createSequence

createTable

createView

delete

dropAllForeignKeyConstraints

dropColumn

Requires an explicit <rollback> block — no automatic inverse.

dropDefaultValue

dropForeignKeyConstraint

dropIndex

dropMaterializedView

dropNotNullConstraint

dropPrimaryKey

dropProcedure

Omit the schemaName attribute when running across schemas.

dropSequence

dropTable

dropUniqueConstraint

dropView

insert

loadData

loadUpdateData

mergeColumns

modifyDataType

renameColumn

renameSequence

renameTable

renameView

setColumnRemarks

setTableRemarks

sql

sqlFile

update

Change Types not supported by Lakebase

  • createTableClone

  • createSnapshotTable

  • createExternalTable

  • disableCheckConstraint

  • enableCheckConstraint

  • dropExternalTable

  • dropSearchIndex

Supported parameters

You can use all normal Liquibase parameters with Lakebase. No extension-specific parameters are required — Lakebase uses the standard PostgreSQL JDBC driver.

Note: Lakebase authenticates via OAuth JWT tokens with approximately a one-hour expiry. Automated pipelines must include a token refresh mechanism before each Liquibase run.

To target a non-public schema, set --defaultSchemaName in the CLI, in flow files, in your liquibase.properties file, or as an environment variable. Both public and non-public schemas have been tested and verified on Lakebase.

Note: Lakebase reports the connecting user without the @domain suffix (e.g., user instead of user@liquibase.com). If you use the runningAs precondition, specify the bare username rather than a full email address.

Supported commands

You can use the Liquibase CLI commands or Liquibase Maven goals with Lakebase:

  • Update Commands

  • Rollback Commands

  • Init Commands

  • Change Tracking Commands

  • Database Inspection Commands

  • Utility Commands

  • Flow Commands

  • Policy Checks Commands

Data type handling

Change Type

Description

Supported

datatypes.arrays

INT[], TEXT[], BOOLEAN[]

Yes

datatypes.binary

BYTEA

Yes

datatypes.bitstring

BIT(8), BIT VARYING(16)

Yes

datatypes.boolean

true, false

Yes

datatypes.character

CHAR, VARCHAR, TEXT

Yes

datatypes.datetime

DATE, TIME, TIMESTAMP, TIMESTAMPTZ, INTERVAL

Yes

datatypes.geometric

POINT, LINE, LSEG, BOX, PATH, POLYGON, CIRCLE

Yes

datatypes.json

JSON, JSONB

Yes

datatypes.money

MONEY column creates successfully but INSERT fails: invalid input syntax for type numeric: "$12.34" — Lakebase maps MONEY to NUMERIC internally and does not accept currency-prefix notation. Use plain numeric literals (e.g., 12.34) in insert or loadData changesets.

No

datatypes.network

INET, CIDR, MACADDR

Yes

datatypes.numeric

INT2/4/8, FLOAT4/8, NUMERIC, DECIMAL

Yes

datatypes.serial

SERIAL, BIGSERIAL, SMALLSERIAL

Yes

datatypes.smallint

SMALLINT

Yes

datatypes.uuid

UUID

Yes

datatypes.xml

XML

Yes

Lakebase features not supported by Liquibase

  • Delta Lake / Unity Catalog Foreign Tables

  • Three-Level Namespace (catalog.schema.table)

  • Vector Search (pgvector)

  • Databricks AI Functions

  • Serverless Compute Cold-Start

  • Unity Catalog Privilege Model