Skip to main content
floo db exposes read and migration access to an app’s managed Postgres. It also exposes preview database branch inspection and reset for pull request previews. pgvector is enabled on every managed Postgres, and the vector type resolves unqualified. floo db query, floo db migrate, and your app’s own connection all see it without a CREATE EXTENSION step or a schema prefix. See Databases → Vector search with pgvector.

query

Run a SQL query against the managed database for an app.

Flags

schema

Print the current database schema for an app.

migrate

Run pending migrations against the managed database.
The CLI ships the migration payload from your current checkout. Use this before or after a deploy when the app depends on a schema change.

connections

Show current Postgres connection usage versus the role’s limit.

Flags

Output

When the role is near capacity (≥75%), the output adds a heads-up about pooling and a one-line Email team@getfloo.com — we can provision a dedicated instance. Use this command when diagnosing too many connections errors or before turning up app autoscaling.

branches list

List the managed Postgres branches backing one preview environment.
The preview argument can be a preview slug, preview URL, source branch, or #123 when it resolves to one preview.

JSON output

The response is agent-safe. It includes branch metadata and reset eligibility, but never plaintext credentials.

branches show

Show one preview database branch.

Flags

branches reset

Drop and recreate one preview-owned managed Postgres branch. Dev and prod are untouched.
Reset is tier 2 because it destroys preview-only data. Non-interactive callers must pass --yes.

Flags

JSON reset fields

Reset is blocked for dev/prod databases, external databases, non-Postgres resources, Redis, Storage, and preview branch rows that are not ready.