---
title: "Managed Postgres: What Lakebase Actually Takes Off Your Plate"
description: "Managed Postgres varies from OS patching alone to operating scaling, failover, backups, recovery, and related database tooling. Lakebase Postgres applies this model to serverless infrastructure, offering automatic scaling, scale-to-zero, PostgreSQL compatibility, automatic snapshots, point-in-time recovery, branching, built-in PgBouncer, and support for extensions including pgvector and PostGIS. Within a region, patching, scaling, failover, and backups run automatically, while encryption, access control, audit visibility, connection pooling, and lakehouse integrations are also addressed. The discussion also stresses checking PostgreSQL versions, configuration, extensions, and migration methods before moving an existing database. Cross-region disaster recovery remains the main exception: it is in Private Preview for AWS, with periodic replication, manual failover, and customer-managed recovery procedures."
---

# Managed Postgres: What Lakebase Actually Takes Off Your Plate

[Databricks](https://yomu.fyi/company/databricks) · Databricks Staff · Sep 14, 2026

**Type:** Explainer

## Summary

Managed Postgres varies from OS patching alone to operating scaling, failover, backups, recovery, and related database tooling. Lakebase Postgres applies this model to serverless infrastructure, offering automatic scaling, scale-to-zero, PostgreSQL compatibility, automatic snapshots, point-in-time recovery, branching, built-in PgBouncer, and support for extensions including pgvector and PostGIS. Within a region, patching, scaling, failover, and backups run automatically, while encryption, access control, audit visibility, connection pooling, and lakehouse integrations are also addressed. The discussion also stresses checking PostgreSQL versions, configuration, extensions, and migration methods before moving an existing database. Cross-region disaster recovery remains the main exception: it is in Private Preview for AWS, with periodic replication, manual failover, and customer-managed recovery procedures.

## Context

The article defines managed Postgres by the operational responsibilities a provider assumes, then evaluates Lakebase against patching, scaling, failover, backups, security, migration, developer tooling, and integrations. Its comparison distinguishes automatic regional operations from cross-region disaster recovery, where customer responsibilities remain.

## Approach / What changed

Lakebase runs PostgreSQL on serverless infrastructure with automatic scaling, including scale-to-zero, automatic PostgreSQL, security, OS, and compute updates, automatic failover to secondary compute within a region, point-in-time restore, scheduled snapshots, built-in PgBouncer, copy-on-write branching, supported extensions, and Databricks lakehouse integrations. Cross-region disaster recovery uses periodic replication but remains AWS-only Private Preview with manual failover and customer-managed recovery procedures.

## Takeaways

- Lakebase automatically handles PostgreSQL, security, OS, and compute updates, scales including to zero when idle, and fails over to secondary compute within a region.
- Point-in-time restore supports configurable 2–30 day history, while scheduled snapshots provide additional backup protection. Cross-region disaster recovery is not equivalent: it requires manual failover and customer-managed procedures.
- Lakebase includes copy-on-write branching, built-in PgBouncer, PostgreSQL roles and permissions, Unity Catalog integrations, and support for extensions such as pgvector and PostGIS.

## FAQ

### What Lakebase operations still require customer involvement?

Cross-region disaster recovery remains in Private Preview for AWS. It uses periodic replication with manual failover and customer-managed recovery procedures, unlike Lakebase’s automatic protection within a region.

### How does Lakebase handle backups and recovery?

Lakebase provides point-in-time restore with configurable 2–30 day history and scheduled snapshots for additional backup protection. Point-in-time recovery can restore the database to a specific moment rather than only the latest snapshot.

### What should teams check before migrating an existing PostgreSQL database?

Teams should check PostgreSQL version support, custom configuration, application assumptions, and every extension the database uses. The source specifically calls out pgvector for AI or embedding workloads and PostGIS for geospatial data.

**Tags:** [Databases](https://yomu.fyi/topic/databases), [Lakebase](https://yomu.fyi/topic/lakebase), [pgvector](https://yomu.fyi/topic/pgvector), [Postgres](https://yomu.fyi/topic/postgres)

- Source: [Databricks](https://www.databricks.com/blog/managed-postgres)
- Source URL: https://www.databricks.com/blog/managed-postgres
- Ingested by Yomu: 2026-09-15T12:03:17.393Z

[Read original post](https://www.databricks.com/blog/managed-postgres)