On this page

Last updated: November 15, 2026

Managed PostgreSQL

Catalog PostgreSQL databases run as managed databases: the platform backs them up continuously, keeps an optional standby ready to take over, and installs updates in a window you choose.

Versions

PostgreSQL 15, 16, 17 and 18 are available. Every managed image includes the pgvector binary; the vector extension is enabled per database. PostGIS and TimescaleDB versions are still offered in the catalog and run with the snapshot backups described in the catalog overview.

Extensions

Open Settings → Postgres extensions and turn on pgvector. The platform installs vector in the current database without recreating the service or restarting PostgreSQL. The status shows whether it is available, enabled, or still being applied. The CLI supports guara db extensions enable vector --service <name> and guara db extensions disable vector --service <name>; guara db extensions --service <name> shows the status. For the API, send PUT /api/v1/projects/:projectId/catalog-services/:serviceId/managed-database/extensions with { "name": "vector", "enabled": true } or false to disable. MCP exposes db_extensions, db_extensions_enable, and db_extensions_disable.

Before disabling it, remove columns, indexes, and other objects that depend on vector. The platform never removes those objects automatically; extension removal remains pending while dependencies exist. For databases on the legacy Alpine engine, open Settings → Migrate to managed Postgres and complete the migration before using this control.

Backups and the recovery window

Two kinds of backup work together, both stored off-site:

BackupWhen
Continuous backupEvery change, copied within minutes
Daily backupA full copy once a day, plus when you click Back up now

Together they let you restore to any moment inside the recovery window. The window length depends on your plan:

ResourceStarterProMaxBusinessEnterprise
PostgreSQL recovery window 3 days 3 days 7 days 7 days 14 days

The Backups tab shows the window as a timeline, with a mark for each daily backup.

Restore to a new database

Restoring never overwrites the database you restore from. Open Backups → Restore to new database, name the new database and choose:

  • Latest — everything backed up so far.
  • A specific moment — any date and time inside the recovery window, in your local time zone. Use this to undo a bad migration or an accidental DELETE.

The new database gets its own credentials. Point your app at it when you have checked the data, then delete whichever copy you no longer need.

Standby instance (high availability)

Turn on Settings → Availability → Standby instance to keep an in-sync copy of the database. If the primary stops responding, the standby takes over automatically and your connection string keeps working.

The standby uses the same CPU, memory and storage as the primary, counted against your plan.

Maintenance window

Minor PostgreSQL updates (security and bug fixes) install automatically in a weekly one-hour window. Pick the day and hour in Settings → Maintenance window, or install a pending update right away with Install now. With a standby the switch takes seconds; without one, expect a short restart.

Major version upgrades

Settings → Version → Upgrade moves the database to a newer major version in place. The platform takes a backup first. The database is unavailable during the upgrade, usually a few minutes, and the upgrade can’t be undone. If anything goes wrong, restore the pre-upgrade backup to a new database.

Connection pool

Apps connect through a connection pool on the same address and port as always. In Settings → Connection pool you can switch to session mode (needed for prepared statements outside transactions and LISTEN/NOTIFY) and tune the number of connections within your plan’s limits.

Database user privileges

Your app’s database user owns its database, but it is not a superuser, so the platform’s backups, standby and upgrades keep working. Three extra privileges are off by default on new databases. Turn them on in Settings → Database user privileges:

PrivilegeAttributeWhat the user can do
Create rolesCREATEROLECreate roles and manage the ones it created, as many migrations do. Available on PostgreSQL 16 and later.
Create databasesCREATEDBCreate more databases on the same server. They share this database’s storage and backups, and connect through the same pool.
Bypass row-level security (RLS)BYPASSRLSIgnore row-level policies, including FORCE ROW LEVEL SECURITY, in every database on this server. Available on all managed PostgreSQL versions.

Changes apply without restarting the database. Turning a privilege off keeps what the user already created: existing roles stay, but the user can no longer change or drop them until you turn Create roles back on.

A restored copy (see Restore to a new database) keeps the privileges of the database it came from. A database moved from the previous engine starts with Create roles and Create databases on (only Create databases on PostgreSQL 15), since its user was a superuser there. Bypass row-level security starts off, including after a migration. Existing databases also keep it off until you explicitly enable it.

Bypass row-level security is for applications that control data access without relying on RLS. It does not grant superuser or table access permissions, remove policies, or disable RLS for other users. It applies to the database user in this service, including connections through the pooler. If the application connects or switches to another role, that role’s attributes apply.

Turning it off restores the normal RLS rules for the database user; table owners still bypass RLS unless FORCE ROW LEVEL SECURITY is set. On PostgreSQL 16+, a user with both CREATEROLE and BYPASSRLS can create other roles with BYPASSRLS. Turning this setting off does not revoke that attribute from those roles.

From the CLI, use guara db privileges, guara db privileges enable --create-role --create-db, guara db privileges enable --bypass-rls, and guara db privileges disable --bypass-rls. See the CLI commands.

Public access

By default, the database is reachable only from inside your project. To connect from outside Guara Cloud — your computer, a CI job, or a BI tool — turn on public access in the service’s Connection tab, under Public access. Public access is available on every plan.

  • TLS is required. Use the public connection string shown in the panel, with sslmode=require.
  • Clients need libpq 14 or newer (PostgreSQL 14+ tools). Older versions don’t send the hostname the platform routes the connection by.
  • Allowed addresses. Restrict access to specific IPv4 addresses or CIDR ranges. With an empty list, any address can try to connect, but only clients with the database password get in.
  • Connection limit. The panel shows how many outside connections the database accepts at once.

Turning public access off, or removing an address from the list, refuses new connections immediately. Sessions already open stay until the client disconnects; restarting the database closes them all.

From the CLI, use guara db public, guara db public enable --allow <address>, and guara db public disable. See the CLI commands.