Skip to main content
PostgreSQL stores hub metadata and workflow persistence.

​
Talks To

​
How It Fits

PostgreSQL is the source of truth for control-plane metadata. Apiserver uses it for the information that defines how the hub is configured and how users interact with it, including identity, authorization, organizations, environments, dashboards, alerts, and integrations. Temporal also uses PostgreSQL for workflow persistence when the bundled Temporal deployment is used. That means PostgreSQL carries both application metadata and durable workflow state, even though high-volume telemetry itself is stored in ClickHouse.

​
Stores

  • Users, roles, and access metadata
  • Organizations and environments
  • Dashboards and alert configuration
  • Integrations and notification settings
  • Temporal workflow persistence

​
Operational Notes

PostgreSQL should be treated as critical durable state. Losing it means losing configuration and metadata even if ClickHouse telemetry data remains intact. For bundled PostgreSQL, the chart uses the CloudNativePG operator to create and manage the PostgreSQL cluster. Operators should protect PostgreSQL with retained persistent volumes and backups. Availability issues here usually appear as UI/API failures, authentication or authorization problems, configuration write failures, or Temporal workflow persistence issues. For production sizing and common operational changes, see PostgreSQL Sizing.