ClickHouse/clickhouse-docs-embeddings huggingface dataset:
Backup and restore

[Edit this page](https://github.com/ClickHouse/clickhouse-docs/blob/main/docs/cloud/managed-postgres/backup-and-restore.md)

[Private preview](https://clickhouse.com/cloud/postgres)

Managed Postgres ensures the safety and availability of your data through automated backups and point-in-time recovery. You can view your backup history and initiate restores from the **Backups** view of your instance.

## Backups[​](#backups "Direct link to Backups")

### Backup frequency[​](#backup-frequency "Direct link to Backup frequency")

Managed Postgres takes daily full backups of your database. In addition to full backups, Write-Ahead Log (WAL) files are archived every 60 seconds or when 16 MB of WAL data accumulates, whichever comes first. This combination of full backups and continuous WAL archiving enables point-in-time recovery to any moment within the retention window.

### Retention period[​](#retention-period "Direct link to Retention period")

Backups are retained for 7 days, providing a sufficient window for recovery in case of data loss or corruption. If you need a longer backup retention period, contact [support](https://clickhouse.com/support/program).

### Storage and durability[​](#storage-and-durability "Direct link to Storage and durability")

Backups are replicated across multiple servers using erasure coding, ensuring they remain accessible even if some storage servers become unavailable. Backup storage is isolated at the bucket level—each Managed Postgres instance has its own dedicated storage bucket, and credentials are scoped to only allow access to that instance's backups.

## Point-in-time recovery[​](#point-in-time-recovery "Direct link to Point-in-time recovery")

Point-in-time recovery allows you to restore your database to any specific moment within the backup retention window. This is useful for recovering from accidental data deletion, corruption, or other issues where you need to roll back to a known good state.

To perform a point-in-time recovery:

1. Navigate to the **Backups** view of your Managed Postgres instance.
2. In the **Point in time recovery** section, select the target date and time (in UTC) you want to restore to.
3. Click **Restore to point in time**.

The restore operation creates a new Managed Postgres instance with the state of your database as it was at the selected point in time. Your original instance remains unchanged, allowing you to verify the restored data before making any decisions about which instance to keep.

- [Backups](#backups)
  - [Backup frequency](#backup-frequency)- [Retention period](#retention-period)- [Storage and durability](#storage-and-durability)- [Point-in-time recovery](#point-in-time-recovery)

Was this page helpful?
PostgreSQL extensions

[Edit this page](https://github.com/ClickHouse/clickhouse-docs/blob/main/docs/cloud/managed-postgres/extensions.md)

[Private preview](https://clickhouse.com/cloud/postgres)

Managed Postgres includes a curated set of extensions to extend the functionality of your database. Below is the list of available extensions.

## Installing extensions[​](#installing-extensions "Direct link to Installing extensions")

To install an extension, connect to your database and run:

```
CREATE EXTENSION extension_name;
```

To see which extensions are currently installed:

```
SELECT * FROM pg_extension;
```

To view all available extensions and their versions:

```
SELECT * FROM pg_available_extensions;
```

## Available extensions[​](#available-extensions "Direct link to Available extensions")
PostgreSQL extensions

## pg\_clickhouse extension[​](#pg-clickhouse "Direct link to pg_clickhouse extension")

The `pg_clickhouse` extension is pre-installed on every Managed Postgres instance. It allows you to query ClickHouse databases directly from PostgreSQL, enabling a unified query layer for both transactions and analytics.

See the [pg\_clickhouse documentation](/docs/integrations/pg_clickhouse) for setup instructions and usage details.

- [Installing extensions](#installing-extensions)- [Available extensions](#available-extensions)- [pg\_clickhouse extension](#pg-clickhouse)

Was this page helpful?
Migrate to Managed Postgres using logical replication

## Next steps[​](#migration-pgdump-pg-restore-next-steps "Direct link to Next steps")

Congratulations! You have successfully migrated your PostgreSQL database to ClickHouse Managed Postgres using pg\_dump and pg\_restore. You're now all set to explore Managed Postgres features and its integration with ClickHouse. Here's a 10 minute quickstart to get you going:

- [Managed Postgres Quickstart Guide](/docs/cloud/managed-postgres/quickstart)

- [Prerequisites](#migration-logical-replication-prerequisites)- [The setup](#migration-logical-replication-setup)- [Schema-only dump of the source database](#migration-logical-replication-schema-dump)
      - [Create a Managed Postgres instance](#migration-pgdump-pg-restore-create-pg)- [Restore the schema to ClickHouse Managed Postgres](#migration-logical-replication-restore-schema)- [Set up logical replication](#migration-logical-replication-setup-replication)
          - [Create a publication on the source database](#migration-logical-replication-create-publication)- [Create a subscription on the target ClickHouse Managed Postgres database](#migration-logical-replication-create-subscription)- [Caveats and considerations](#migration-logical-replication-caveats)- [Next steps](#migration-pgdump-pg-restore-next-steps)

Was this page helpful?
Scaling

- Scale CDC workers from 1 to 24 CPU cores
- Memory automatically scales at 4x the CPU core count
- Adjust scaling via the [ClickPipes OpenAPI](/docs/integrations/clickpipes/postgres/scaling)

This allows you to optimize the replication throughput separately from your Postgres instance resources.

## Autoscaling (roadmap)[​](#autoscaling "Direct link to Autoscaling (roadmap)")

Coming soon

Automatic storage scaling is on the roadmap for Managed Postgres. This feature will automatically increase instance size as your database grows, eliminating the need for manual intervention.

## Additional resources[​](#resources "Direct link to Additional resources")

- [Settings and configuration](/docs/cloud/managed-postgres/settings)
- [Read replicas](/docs/cloud/managed-postgres/read-replicas)
- [High availability](/docs/cloud/managed-postgres/high-availability)

- [Instance types and flexibility](#instance-types)
  - [Choosing the right instance type](#choosing-instance)- [How scaling works](#how-scaling-works)
    - [Scaling process](#scaling-process)- [Scaling duration](#scaling-duration)- [Parallel restore with WAL-G](#parallel-restore)- [Initiating a scaling operation](#initiating-scaling)- [Scaling strategies](#scaling-strategies)
      - [Vertical scaling](#vertical-scaling)- [Read replicas for horizontal scaling](#read-replicas)- [CDC scaling for ClickHouse integration](#cdc-scaling)- [Autoscaling (roadmap)](#autoscaling)- [Additional resources](#resources)

Was this page helpful?
Settings

[Edit this page](https://github.com/ClickHouse/clickhouse-docs/blob/main/docs/cloud/managed-postgres/settings.md)

[Private preview](https://clickhouse.com/cloud/postgres)

You can modify configuration parameters and manage instance settings for your Managed Postgres instance through the **Settings** tab in the sidebar.

## Changing configuration parameters[​](#changing-configuration "Direct link to Changing configuration parameters")

To modify a parameter, select the **Edit parameters** button. Select the parameters you need to modify and change their values accordingly. Once you're satisfied with your changes, press the **Save Changes** button.

All changes made to the configuration parameters are typically persisted to the instance within one minute. Some parameters require a database restart to take effect. These changes will be applied after the next restart, which you can trigger manually from the **Service actions** toolbar.

## Service actions and scaling[​](#service-actions "Direct link to Service actions and scaling")

The **Service actions** toolbar provides controls for managing your Managed Postgres instance:

- **Reset password**: Update the superuser password (only when the instance is `Running`)
- **Restart**: Restart the database instance (only when the instance is `Running`)
- **Delete**: Delete the instance

The **Scaling** section allows you to change the instance types of your primary and standbys to increase or decrease computing resources and storage capacity. Behind the scenes, new instances will be provisioned and then take over after they've caught up with the current primary. The failover process will interrupt all current connections and lead to brief downtime.

Tip

For safety reasons, you may not be able to switch to instance types whose storage is close to your current used storage capacity. Always opt for instance types with headroom over your current used capacity to avoid any issues.

## IP filters[​](#ip-filters "Direct link to IP filters")

IP filters control which source IP addresses are permitted to connect to your Managed Postgres instance.

To configure IP filters:

1. Navigate to the **Settings** tab
2. Under **IP Filters**, click **Edit**
3. Add IP addresses or CIDR ranges that should be allowed to connect
4. Click **Save** to apply the changes

You can specify individual IP addresses or use CIDR notation for IP ranges (e.g., `192.168.1.0/24`). You can also select **Anywhere** or **Nowhere** as a shortcut for fully opening or closing the instance to the world.

Note

If no IP filters are configured, connections from all IP addresses are permitted. For production workloads, we recommend restricting access to known IP addresses.

- [Changing configuration parameters](#changing-configuration)- [Service actions and scaling](#service-actions)- [IP filters](#ip-filters)

Was this page helpful?
Upgrades

[Edit this page](https://github.com/ClickHouse/clickhouse-docs/blob/main/docs/cloud/managed-postgres/upgrades.md)

[Private preview](https://clickhouse.com/cloud/postgres)

Managed Postgres handles PostgreSQL version upgrades to keep your instances secure and up to date. Both minor and major version upgrades are supported with minimal disruption.

## Minor version upgrades[​](#minor-version-upgrades "Direct link to Minor version upgrades")

Minor version upgrades (e.g., 16.4 to 16.5) include bug fixes and security patches. These are performed via failover and typically result in only a brief disconnect, often lasting just a few seconds.

For instances with [standbys](/docs/cloud/managed-postgres/high-availability) enabled, the upgrade is applied to the standby first, followed by a failover to minimize downtime.

## Major version upgrades[​](#major-version-upgrades "Direct link to Major version upgrades")

Major version upgrades (e.g., 16.x to 17.x) also involve only a few seconds of downtime, following a similar failover-based approach.

## Maintenance windows[​](#maintenance-windows "Direct link to Maintenance windows")

Managed Postgres supports maintenance windows so that upgrades and other maintenance operations can be scheduled at a time that's least disruptive to your workload. UI support for configuring maintenance windows is coming soon. In the meantime, contact [support](https://clickhouse.com/support/program) to set up a maintenance window for your instance.

- [Minor version upgrades](#minor-version-upgrades)- [Major version upgrades](#major-version-upgrades)- [Maintenance windows](#maintenance-windows)

Was this page helpful?
Monitoring in the ClickHouse Cloud Console

| --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | | Network send bytes/sec `NetworkSendBytes` `asynchronous_metric_log` Sum / bucketSizeSeconds|  |  |  |  |  |  |  |  |  |  |  |  | | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | | Concurrent TCP connections `CurrentMetric_TCPConnection` `metric_log` |  |  |  |  |  |  |  |  | | --- | --- | --- | --- | --- | --- | --- | --- | | Concurrent MySQL connections `CurrentMetric_MySQLConnection` `metric_log` |  |  |  |  | | --- | --- | --- | --- | | Concurrent HTTP connections `CurrentMetric_HTTPConnection` `metric_log`  | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
Monitoring in the ClickHouse Cloud Console

For detailed information on each visualization and how to use them for troubleshooting, see the [advanced dashboard documentation](/docs/cloud/manage/monitor/advanced-dashboard).

## Query insights[​](#query-insights "Direct link to Query insights")

The **Query Insights** feature makes ClickHouse's built-in query log easier to use through various visualizations and tables. ClickHouse's `system.query_log` table is a key source of information for query optimization, debugging, and monitoring overall cluster health and performance.

After selecting a service, the **Monitoring** navigation item in the left sidebar expands to reveal a **Query insights** sub-item:

### Top-level metrics[​](#top-level-metrics "Direct link to Top-level metrics")

The stat boxes at the top represent basic query metrics over the selected time period. Beneath them, time-series charts show query volume, latency, and error rate broken down by query kind (select, insert, other). The latency chart can be adjusted to display p50, p90, and p99 latencies:

### Recent queries[​](#recent-queries "Direct link to Recent queries")

A table displays query log entries grouped by normalized query hash and user over the selected time window. Recent queries can be filtered and sorted by any available field, and the table can be configured to display or hide additional fields such as tables, p90, and p99 latencies:

### Query drill-down[​](#query-drill-down "Direct link to Query drill-down")

Selecting a query from the recent queries table will open a flyout containing metrics and information specific to the selected query:

All metrics in the **Query info** tab are aggregated metrics, but we can also view metrics from individual runs by selecting the **Query history** tab:

From this pane, the `Settings` and `Profile Events` items for each query run can be expanded to reveal additional information.

## Related pages[​](#related "Direct link to Related pages")

- [Notifications](/docs/cloud/notifications) — Configure alerts for scaling events, errors, and billing
- [Advanced dashboard](/docs/cloud/manage/monitor/advanced-dashboard) — Detailed reference for each dashboard visualization
- [Querying system tables](/docs/cloud/monitoring/system-tables) — Run custom SQL queries against system tables for deep introspection
- [Prometheus endpoint](/docs/integrations/prometheus) — Export metrics to Grafana, Datadog, or other Prometheus-compatible tools

- [Dashboards](#dashboards)
  - [Service health](#service-health)- [Resource utilization](#resource-utilization)- [Advanced dashboard](#advanced-dashboard)- [Query insights](#query-insights)
    - [Top-level metrics](#top-level-metrics)- [Recent queries](#recent-queries)- [Query drill-down](#query-drill-down)- [Related pages](#related)

Was this page helpful?
Community and partner integrations

[Edit this page](https://github.com/ClickHouse/clickhouse-docs/blob/main/docs/cloud/features/08_monitoring/integrations.md)

## Direct Datadog integration[​](#direct-datadog "Direct link to Direct Datadog integration")

Datadog offers a ClickHouse Monitoring plugin for its agent which queries system tables directly. This integration provides comprehensive database monitoring with cluster awareness through `clusterAllReplicas` functionality.

Not recommended for ClickHouse Cloud

The direct Datadog agent integration that queries system tables isn't recommended for ClickHouse Cloud deployments due to incompatibility with cost-optimizing idle behavior and operational limitations of the cloud proxy layer.

Instead, use the Datadog [Agent](https://docs.datadoghq.com/agent/?tab=Linux) and [OpenMetrics integration](https://docs.datadoghq.com/integrations/openmetrics/) to collect metrics from the ClickHouse Cloud Prometheus endpoint. This approach respects service idling behavior and maintains operational separation between monitoring and production workloads. For configuration guidance, see [Datadog's Prometheus and OpenMetrics integration documentation](https://docs.datadoghq.com/integrations/openmetrics/).

For Prometheus endpoint setup details, see the [Prometheus integration page](/docs/integrations/prometheus#integrating-with-datadog).

## Community monitoring solutions[​](#community-monitoring "Direct link to Community monitoring solutions")

The ClickHouse community has developed comprehensive monitoring solutions that integrate with popular observability stacks. [ClickHouse Monitoring](https://github.com/duyet/clickhouse-monitoring) provides a complete monitoring setup with pre-built dashboards. This open source project offers a quick-start approach for teams looking to implement ClickHouse monitoring with established best practices and proven dashboard configurations.

Note

Like other direct database monitoring approaches, this solution queries ClickHouse system tables directly, which prevents instances from idling and impacts cost optimization.

## Billing and Usage API[​](#billing-usage-api "Direct link to Billing and Usage API")

The Billing & Usage API can be used to programmatically access your Cloud organization's billing and usage records. This is useful for building custom cost monitoring dashboards or integrating billing data into existing financial reporting workflows.

For full API reference, see the [Billing API documentation](https://clickhouse.com/docs/cloud/manage/api/swagger#tag/Billing).

- [Direct Datadog integration](#direct-datadog)- [Community monitoring solutions](#community-monitoring)- [Billing and Usage API](#billing-usage-api)

Was this page helpful?
[Edit this page](https://github.com/ClickHouse/clickhouse-docs/blob/main/docs/cloud/onboard/01_discover/01_what_is.md)

## What is ClickHouse Cloud?[​](#what-is-clickhouse-cloud "Direct link to What is ClickHouse Cloud?")

ClickHouse Cloud is a fully managed cloud service created by the original creators
of ClickHouse, the fastest and most popular open-source columnar online analytical
processing database.

With Cloud, infrastructure, maintenance, scaling, and operations are taken care of
for you, so that you can focus on what matters most to you, which is building value
for your organization and your customers faster.

## Benefits of ClickHouse Cloud[​](#benefits-of-clickhouse-cloud "Direct link to Benefits of ClickHouse Cloud")

ClickHouse Cloud offers several major benefits over the open-source version:

- **Fast time to value**: Start building instantly without having to size and scale your cluster.
- **Seamless scaling**: Automatic scaling adjusts to variable workloads so you don't have to over-provision for peak usage.
- **Serverless operations**: Sit back while we take care of sizing, scaling, security, reliability, and upgrades.
- **Transparent pricing**: Pay only for what you use, with resource reservations and scaling controls.
- **Total cost of ownership**: Best price / performance ratio and low administrative overhead.
- **Broad ecosystem**: Bring your favorite data connectors, visualization tools, SQL and language clients with you.

## Comparison of self-managed ClickHouse and ClickHouse Cloud[​](#oss-vs-clickhouse-cloud "Direct link to Comparison of self-managed ClickHouse and ClickHouse Cloud")
Private networking setup

[Edit this page](https://github.com/ClickHouse/clickhouse-docs/blob/main/docs/cloud/guides/infrastructure/01_deployment_options/byoc/03_onboarding/03_network_setup/index.md)

ClickHouse BYOC supports various private networking options to enhance security and enable direct connectivity for your services. This guide walks you through the recommended approaches for securely connecting ClickHouse Cloud deployments in your own AWS or GCP account to other networks or services, such as your internal applications or analytics tools. We cover options such as VPC Peering, AWS PrivateLink, and GCP Private Service Connect, and outline the main steps and considerations for each.

If you require a private network connection to your ClickHouse BYOC deployment, follow the steps in the guides or consult ClickHouse Support for assistance with more advanced scenarios.

Was this page helpful?
BYOC AWS private networking setup

- **Public endpoint**: `h5ju65kv87.mhp0y4dmph.us-west-2.aws.clickhouse-byoc.com`
- **PrivateLink endpoint**: `h5ju65kv87.vpce.mhp0y4dmph.us-west-2.aws.clickhouse-byoc.com`

DNS resolution in your VPC will automatically route traffic through the PrivateLink endpoint when you use the `vpce` subdomain format.

### PrivateLink Access Control[​](#privatelink-access-control "Direct link to PrivateLink Access Control")

Access to ClickHouse services via PrivateLink is controlled at two levels:

1. **Istio Authorization Policy**: ClickHouse Cloud's service-level authorization policies
2. **VPC Endpoint Security Group**: The security group attached to your VPC endpoint controls which resources in your VPC can use the endpoint

Note

The private load balancer's "Enforce inbound rules on PrivateLink traffic" feature is disabled, so access is controlled by Istio authorization policies and your VPC endpoint's security group only.

### PrivateLink DNS[​](#privatelink-dns "Direct link to PrivateLink DNS")

PrivateLink DNS for BYOC endpoints (using the `*.vpce.{subdomain}` format) leverages AWS PrivateLink's built-in "Private DNS names" feature. No Route53 records are required—DNS resolution happens automatically when:

- "Private DNS names" is enabled on your VPC endpoint
- Your VPC has "DNS Hostnames" enabled

This ensures that connections using the `vpce` subdomain automatically route through the PrivateLink endpoint without additional DNS configuration.

- [Prerequisites](#common-prerequisites)
  - [Enable private load balancer for ClickHouse BYOC](#step-enable-private-load-balancer-for-clickhouse-byoc)- [Set up VPC peering](#aws-vpc-peering)
    - [Create a peering connection](#step-1-create-a-peering-connection)- [Accept the peering connection request](#step-2-accept-the-peering-connection-request)- [Add destination to ClickHouse VPC route tables](#step-3-add-destination-to-clickhouse-vpc-route-tables)- [Add destination to the target VPC route tables](#step-4-add-destination-to-the-target-vpc-route-tables)- [Edit security group to allow peered VPC access](#step-5-edit-security-group-to-allow-peered-vpc-access)- [Set up PrivateLink](#setup-privatelink)
      - [Request PrivateLink Setup](#step-1-request-privatelink-setup)- [Create an Endpoint in Your VPC](#step-2-create-endpoint)- [Add Endpoint ID to Service Allowlist](#step-3-add-endpoint-id-allowlist)- [Connect to ClickHouse via PrivateLink](#step-4-connect-via-privatelink)- [PrivateLink Access Control](#privatelink-access-control)- [PrivateLink DNS](#privatelink-dns)

Was this page helpful?