Docs/Engines/Google AlloyDB

Google AlloyDB

AlloyDB for PostgreSQL is wire-compatible with PostgreSQL and behaves identically here. Setting type: alloydb records the engine you actually run in history and in reports.

type

alloydb

Driver

psycopg

DDL

Transactional

Config class

PostgreSQL

Install

pip install "dblift[alloydb]"

Connection URL

postgresql+psycopg://user:password@10.0.0.5:5432/app

A plain postgresql:// URL works — DBLift adds the psycopg driver.

dblift.yaml

database:
  type: alloydb
  url: "postgresql+psycopg://db.internal:5432/app"
  schema: "public"
  ssl_mode: "require"
migrations:
  directory: "./migrations"

Engine settings

KeyDefaultEffect

schemapublicSets the connection's search_path, so unqualified objects land here.

ssl_mode—Passed through as PostgreSQL's sslmode: require, verify-ca, verify-full.

connection_timeout30Seconds to wait for a connection, sent as connect_timeout.

extra_params{}Any other libpq parameter, appended to the connection URL.

Behaviour notes

No declared differences from PostgreSQL.

Transactional DDL, concurrent index builds and cascading drops all behave as on PostgreSQL.

The PostgreSQL page is the reference.

This page carries the identity and the install extra only.

PreviousAurora PostgreSQL NextNeon