render postgres exposes top-level Postgres commands

Introduced 2026-06-29 · score 0.93

HOW TO USE IT

When managing a Render Postgres resource, use the CLI commands available in version 2.21.0 or later; `render pg` is the documented shorthand. Create a database with `render pg create --name <name> --region <region> --version <major> --plan <plan> --confirm`, or use the documented `list` and `get` commands to inspect resources.

WHY THIS HELPS

Manage a Postgres resource from the Render CLI.

REQUIREMENTS AND LIMITATIONS

• Version: v2.21.0
• Availability: generally available
• <postgresID|postgresName> (required): Target database ID or name for `get`; names are looked up in the active workspace.
• --name <name>: Set the database name; generated if omitted.
• --region <region>: Set the region; server picks one if omitted.
• --version <major>: Set the Postgres major version; defaults to 18 in the current reference.
• --plan <plan>: Choose the Postgres plan.
• --confirm: Skip confirmation prompts; with create, skip the wizard and create immediately from flags and defaults.
• Prerequisite: Render CLI version 2.21.0 or later.
• Prerequisite: Authenticate with `render login`, or provide a Render API key for CLI authentication.
• Docs conflict: The card says top-level `render postgres` is available. The current generated CLI reference (v2.29.0) documents Postgres commands under `pg` and does not document `postgres`; it is newer than the card version.

FIRST-PARTY EVIDENCE

• https://github.com/render-oss/cli/releases/tag/v2.21.0
• https://render.com/changelog/manage-postgres-and-key-value-instances-using-the-render-cli
• https://render.com/docs/cli-reference
• https://render.com/docs/cli

Check the installed version and the source before using it. Entry JSON

Report a problem with this card