Skip to content
Stackship documentation Svenska

PostgreSQL

Managed PostgreSQL clusters run by the CloudNativePG operator — instances, storage, compute plans, connections, backups and the Data Explorer.

  • API reference — Every HTTP endpoint of the db-postgres module: authentication, IAM action, parameters, bodies and status codes.
  • What PostgreSQL backups need — How managed PostgreSQL clusters archive to the platform's backup target — the dependencies, the objects the operator projects into each namespace, the paths and retention — and what happens without a target.
  • Turn on backups — Turn backups on for a PostgreSQL cluster, set when its scheduled snapshot runs, and turn them off again.
  • Backups and point-in-time recovery — How PostgreSQL backups work — the continuous archive, snapshots, the recovery window, retention — and what a restore does to the cluster.
  • Take and restore snapshots — Take a snapshot of a PostgreSQL cluster, restore it in place, restore to a point in time, and delete snapshots — in the portal or with the CLI.
  • Compute plans and parameters — The PostgreSQL compute plans — CPU, memory, storage, instances — the parameters each plan tunes, what a change restarts, and the rules for your own parameters.
  • Configuration reference — Configuration keys of the db-postgres module: sections, environment variables, types and defaults.
  • Connect to a cluster — Get a cluster's connection string, choose the URI or the key=value form, and hand it to a workload through a vault — directly, through the pooler or to the replicas.
  • Create a cluster — Create a PostgreSQL cluster in the portal — name and placement, version and database, compute plan, storage and instances, pooling, backups and monitoring — or with the CLI or the API.
  • Use the Data Explorer — Browse and edit rows and run SQL against a PostgreSQL cluster in the portal — who may, what is checked before a statement runs, dry runs, limits and the audit trail.
  • Instances and high availability — How a PostgreSQL cluster's primary and replicas work, which service leads where, what happens on a failover, a restart and a stop, and what it means for connections.
  • PostgreSQL — Managed PostgreSQL clusters run by the CloudNativePG operator — instances, storage, compute plans, connections, backups and the Data Explorer.
  • Manage a cluster — Start, stop and restart a PostgreSQL cluster, change its compute plan, instances and storage, set pooling and PostgreSQL parameters, upgrade its major version and delete it.
  • Names, limits and statuses — The rules for PostgreSQL cluster and database names, the supported versions, the limits on instances, storage, pooling and the Data Explorer, and the statuses a cluster shows.
  • Network access — Choose which workloads may reach a PostgreSQL cluster, expose it outside the Kubernetes cluster on a load balancer, and restrict outside access to address ranges.
  • Permissions — The actions that govern PostgreSQL clusters, the roles that hold them, and the permission each Data Explorer statement needs.
  • Manage the compute plans — Where the PostgreSQL compute plans are stored, which of them the module resets on every start, how to add a plan of your own, and where the storage classes come from.
  • Create schemas and tables — Create a schema or a table in a PostgreSQL cluster from the portal's Data Explorer — names, columns, types, keys, the dry run — who owns what you create, and how to drop it.
  • Find out why a cluster is not ready — Follow a PostgreSQL cluster's operation instance by instance, check its health, and act on the reasons the platform gives for an instance that does not start.