Restructure Managed Postgres sidebar and add migration overview

.github/pull_request_template.md

@@ -3,5 +3,5 @@
 
 ## Checklist
 - [ ] Delete items not relevant to your PR
-- [ ] URL changes should add a redirect to the old URL via https://github.com/ClickHouse/clickhouse-docs/blob/main/docusaurus.config.js
+- [ ] URL changes should add a redirect to the old URL via https://github.com/ClickHouse/clickhouse-docs/blob/main/vercel.json
 - [ ] If adding a new integration page, also add an entry to the integrations list here: https://github.com/ClickHouse/clickhouse-docs/blob/main/docs/integrations/index.mdx

docs/cloud/managed-postgres/extensions.md

@@ -137,7 +137,7 @@ SELECT * FROM pg_available_extensions;
 
 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](/integrations/pg_clickhouse) for setup instructions and usage details.
+See the [pg_clickhouse documentation](/cloud/managed-postgres/extensions/pg_clickhouse) for setup instructions and usage details.
 
 ## pg_stat_ch extension {#pg-stat-ch}
 

docs/integrations/tools/data-integration/pg_clickhouse/introduction.md → docs/cloud/managed-postgres/extensions/pg_clickhouse/introduction.md

@@ -1,7 +1,7 @@
 ---
 sidebar_label: 'Introduction'
 description: 'Run analytics queries on ClickHouse right from PostgreSQL without rewriting any SQL'
-slug: '/integrations/pg_clickhouse'
+slug: '/cloud/managed-postgres/extensions/pg_clickhouse'
 title: 'pg_clickhouse reference documentation'
 doc_type: 'landing-page'
 keywords: ['PostgreSQL', 'Postgres', 'FDW', 'foreign data wrapper', 'pg_clickhouse', 'extension']
@@ -20,13 +20,13 @@
 tables, preserving your existing code base while pushing execution down to
 ClickHouse.
 
-## Getting Started {#getting-started}
+## Getting started {#getting-started}
 
 The simplest way to try pg_clickhouse is the [Docker image], which contains
 the standard PostgreSQL Docker image with the pg_clickhouse and [re2]
 extensions:
 
 ```sh
 docker run --name pg_clickhouse -e POSTGRES_PASSWORD=my_pass \
        -d ghcr.io/clickhouse/pg_clickhouse:18
 docker exec -it pg_clickhouse psql -U postgres -c 'CREATE EXTENSION pg_clickhouse'
@@ -35,9 +35,9 @@
 See the [tutorial] to get started importing ClickHouse tables and pushing down
 queries.
 
-## Test Case: TPC-H {#test-case-tpc-h}
+## Test case: TPC-H {#test-case-tpc-h}
 
 This table compares [TPC-H] query performance between regular PostgreSQL
 tables and pg_clickhouse connected to ClickHouse, both loaded at scaling
 factor 1; ✔︎ indicates full pushdown, while a dash indicates a query
 cancellation after 1m. All tests run on a MacBook Pro M4 Max with 36 GB of
@@ -68,20 +68,20 @@
 | [Query 21] |    1349 ms |       4434 ms |          |
 | [Query 22] |     258 ms |       1415 ms |          |
 
-### Compile From Source {#compile-from-source}
+### Compile from source {#compile-from-source}
 
 #### General Unix {#general-unix}
 
 The PostgreSQL and curl development packages include `pg_config` and
 `curl-config` in the path, so you should be able to just run `make` (or
 `gmake`), then `make install`, then in your database
 `CREATE EXTENSION pg_clickhouse`.
 
 #### Debian / Ubuntu / APT {#debian--ubuntu--apt}
 
 See [PostgreSQL Apt] for details on pulling from the PostgreSQL Apt repository.
 
 ```sh
 sudo apt install \
   postgresql-server-18 \
   libcurl4-openssl-dev \
@@ -94,7 +94,7 @@
 
 #### RedHat / CentOS / Yum {#redhat--centos--yum}
 
 ```sh
 sudo yum install \
   postgresql-server \
   libcurl-devel \
@@ -107,13 +107,13 @@
 
 See [PostgreSQL Yum] for details on pulling from the PostgreSQL Yum repository.
 
-#### Install From PGXN {#install-from-pgxn}
+#### Install from PGXN {#install-from-pgxn}
 
 With the above dependencies satisfied use the [PGXN client] (available as
 [Homebrew], [Apt] and Yum packages named `pgxnclient`) to download, compile,
 and install `pg_clickhouse`:
 
 ```sh
 pgxn install pg_clickhouse
 ```
 
@@ -281,10 +281,10 @@
 
   [pg_clickhouse]: https://github.com/clickHouse/pg_clickhouse
     "pg_clickhouse on GitHub"
-  [import foreign tables]: /integrations/pg_clickhouse/reference#import-foreign-schema
+  [import foreign tables]: /cloud/managed-postgres/extensions/pg_clickhouse/reference#import-foreign-schema
   [Docker image]: https://github.com/ClickHouse/pg_clickhouse/pkgs/container/pg_clickhouse
     "Latest Docker release"
-  [tutorial]: /integrations/pg_clickhouse/tutorial "pg_clickhouse Tutorial"
+  [tutorial]: /cloud/managed-postgres/extensions/pg_clickhouse/tutorial "pg_clickhouse Tutorial"
   [PostgreSQL Apt]: https://wiki.postgresql.org/wiki/Apt
   [PostgreSQL Yum]: https://yum.postgresql.org
   [PGXN client]: https://pgxn.github.io/pgxnclient/ "PGXN Client’s documentation"

docs/integrations/tools/data-integration/pg_clickhouse/reference.md → docs/cloud/managed-postgres/extensions/pg_clickhouse/reference.md

@@ -1,7 +1,7 @@
 ---
 sidebar_label: 'Reference'
 description: 'Complete reference documentation for pg_clickhouse'
-slug: '/integrations/pg_clickhouse/reference'
+slug: '/cloud/managed-postgres/extensions/pg_clickhouse/reference'
 title: 'pg_clickhouse reference documentation'
 doc_type: 'reference'
 keywords: ['PostgreSQL', 'Postgres', 'FDW', 'foreign data wrapper', 'pg_clickhouse', 'extension']
@@ -13,7 +13,7 @@
 on ClickHouse databases, including a [foreign data wrapper]. It supports
 PostgreSQL 13 and higher and ClickHouse 23 and higher.
 
-## Getting Started {#getting-started}
+## Getting started {#getting-started}
 
 The simplest way to try pg_clickhouse is the [Docker image], which contains
 the standard PostgreSQL Docker image with the pg_clickhouse and [re2][re2
@@ -40,7 +40,7 @@
 IMPORT FOREIGN SCHEMA taxi FROM SERVER taxi_srv INTO taxi;
 ```
 
-## Versioning Policy {#versioning-policy}
+## Versioning policy {#versioning-policy}
 
 pg_clickhouse adheres to [Semantic Versioning] for its public releases.
 
@@ -68,7 +68,7 @@
 the extension must run `ALTER EXTENSION pg_clickhouse UPDATE` to benefit from
 the upgrade.
 
-## DDL SQL Reference {#ddl-sql-reference}
+## DDL SQL reference {#ddl-sql-reference}
 
 The following SQL [DDL] expressions use pg_clickhouse.
 
@@ -132,9 +132,9 @@
 The supported options are:
 
 * `driver`: The ClickHouse connection driver to use, either "binary" or
     "http". **Required.**
 * `dbname`: The ClickHouse database to use upon connecting. Defaults to
     "default".
 * `fetch_size`: Approximate batch size in bytes for HTTP streaming. Batches
   split on row boundaries. Defaults to `50000000` (50 MB). `0` disables
   streaming and buffers the full response. Foreign tables can override this
@@ -185,7 +185,7 @@
 
 The supported options are:
 
 * `user`: The name of the ClickHouse user. Defaults to "default".
 * `password`: The password of the ClickHouse user.
 
 ### ALTER USER MAPPING {#alter-user-mapping}
@@ -370,7 +370,7 @@
 DROP FOREIGN TABLE acts CASCADE;
 ```
 
-## DML SQL Reference {#dml-sql-reference}
+## DML SQL reference {#dml-sql-reference}
 
 The SQL [DML] expressions below may use pg_clickhouse. Examples depend on
 these ClickHouse tables:
@@ -666,7 +666,7 @@
 > **⚠️ Batch API Limitations**
 >
 > pg_clickhouse hasn't yet implemented support for the PostgreSQL FDW batch
 > insert API. Thus [COPY] currently uses [INSERT](#insert) statements to
 > insert records. This will be improved in a future release.
 
 ### LOAD {#load}
@@ -679,7 +679,7 @@
 ```
 
 It's not normally necessary to use [LOAD], as Postgres will automatically load
-pg_clickhouse the first time any of of its features (functions, foreign
+pg_clickhouse the first time any of its features (functions, foreign
 tables, etc.) are used.
 
 The one time it may be useful to [LOAD] pg_clickhouse is to [SET](#set)
@@ -821,7 +821,7 @@
 Useful to save memory and load overhead for every session, but requires the
 cluster to be restart when the library is updated.
 
-## Data Types {#data-types}
+## Data types {#data-types}
 
 pg_clickhouse maps the following ClickHouse data types to PostgreSQL data
 types. [IMPORT FOREIGN SCHEMA](#import-foreign-schema) uses the first type in
@@ -972,7 +972,7 @@
 only for binary data, and never switch between them.
 :::
 
-## Function and Operator Reference {#function-and-operator-reference}
+## Function and operator reference {#function-and-operator-reference}
 
 ### Functions {#functions}
 

docs/integrations/tools/data-integration/pg_clickhouse/tutorial.md → docs/cloud/managed-postgres/extensions/pg_clickhouse/tutorial.md

@@ -1,7 +1,7 @@
 ---
 sidebar_label: 'Tutorial'
 description: 'Learn how to connect pg_clickhouse to ClickHouse and query a New York City taxi example dataset.'
-slug: '/integrations/pg_clickhouse/tutorial'
+slug: '/cloud/managed-postgres/extensions/pg_clickhouse/tutorial'
 title: 'pg_clickhouse tutorial'
 doc_type: 'guide'
 keywords: ['PostgreSQL', 'Postgres', 'FDW', 'foreign data wrapper', 'pg_clickhouse', 'extension', 'tutorial', 'taxi']
@@ -23,7 +23,7 @@
 docker exec -it clickhouse clickhouse-client
 ```
 
-## Create a Table {#create-a-table}
+## Create a table {#create-a-table}
 
 Let's borrow from the [ClickHouse tutorial] to create a simple database with The New York
 City taxi dataset:
@@ -88,7 +88,7 @@
 ORDER BY pickup_datetime;
 ```
 
-## Add the Data Set {#add-the-data-set}
+## Add the data set {#add-the-data-set}
 
 And then import the data:
 
@@ -212,7 +212,7 @@
 IMPORT FOREIGN SCHEMA taxi FROM SERVER taxi_srv INTO taxi;
 ```
 
 And now the table should be imported: In [psql], use `\det+` to see it:
 
 ```pgsql
 taxi=# \det+ taxi.*
@@ -223,7 +223,7 @@
 (1 row)
 ```
 
 Success! Use `\d` to show all the columns:
 
 ```pgsql
 taxi=# \d taxi.trips
@@ -462,14 +462,14 @@
     Time: 17.450 ms
     ```
 
-## Create a Dictionary {#create-a-dictionary}
+## Create a dictionary {#create-a-dictionary}
 
 Create a dictionary associated with a table in your ClickHouse service. The
 table and dictionary are based on a CSV file that contains a row for each
 neighborhood in New York City.
 
 The neighborhoods are mapped to the names of the five New York City boroughs
 (Bronx, Brooklyn, Manhattan, Queens and Staten Island), as well as Newark
 Airport (EWR).
 
 Here's an excerpt from the CSV file you're using in table format. The
@@ -621,7 +621,7 @@
     Time: 2.012 ms
     ```
 
-2.  This query returns rows for the the 1000 trips with the highest tip
+2.  This query returns rows for the 1000 trips with the highest tip
     amount, then performs an inner join of each row with the dictionary:
 
     ```sql

docs/cloud/managed-postgres/migrations/overview.md

@@ -0,0 +1,69 @@
+---
+slug: /cloud/managed-postgres/migrations/overview
+sidebar_label: 'Overview'
+title: 'Managed Postgres data migration'
+description: 'Compare the four migration paths into ClickHouse Managed Postgres and pick the one that fits your source database and downtime requirements.'
+keywords: ['managed postgres', 'migration', 'postgres migration', 'clickpipes', 'peerdb', 'pg_dump', 'pg_restore', 'logical replication']
+doc_type: 'guide'
+---
+
+import BetaBadge from '@theme/badges/BetaBadge';
+
+# Managed Postgres data migration
+
+<BetaBadge link="https://clickhouse.com/cloud/postgres" galaxyTrack={true} galaxyEvent="docs.managed-postgres.migration-overview-beta" />
+
+You can migrate to Managed Postgres through four different paths. Which one
+fits depends on whether you need ongoing replication, what source you're
+migrating from, and how much downtime your application can tolerate during
+cutover.
+
+| Method                                                                                | Ongoing replication (CDC) | Where it runs              | Best for                                                                  |
+| ------------------------------------------------------------------------------------- | ------------------------- | -------------------------- | ------------------------------------------------------------------------- |
+| [ClickPipes](/cloud/managed-postgres/migrations/clickpipes)                           | Yes                       | ClickHouse Cloud console   | Most migrations — guided wizard with initial load and CDC out of the box  |
+| [PeerDB](/cloud/managed-postgres/migrations/peerdb)                                   | Yes                       | Self-hosted (Docker)       | Sources or workflows not covered by the ClickPipes UI                     |
+| [pg_dump and pg_restore](/cloud/managed-postgres/migrations/pg_dump-pg_restore)       | No                        | Your local machine         | One-time moves of small or static datasets where downtime is acceptable   |
+| [Logical replication](/cloud/managed-postgres/migrations/logical-replication)         | Yes                       | Source and target Postgres | Direct control over native Postgres replication, no third-party tooling   |
+
+## ClickPipes {#clickpipes}
+
+[ClickPipes](/cloud/managed-postgres/migrations/clickpipes) is the recommended
+path for most migrations. It runs entirely inside the ClickHouse Cloud console
+and walks you through connecting to the source, exporting and importing the
+schema, and starting an initial load with or without CDC. Pre-built source
+connectors cover Amazon RDS, Aurora, Supabase, Google Cloud SQL, Azure
+Flexible Server, Neon, Crunchy Bridge, TimescaleDB, and any generic Postgres
+instance.
+
+## PeerDB {#peerdb}
+
+[PeerDB](/cloud/managed-postgres/migrations/peerdb) is a self-hosted migration
+tool you run via Docker. Use it when your source or workflow isn't a fit for
+the ClickPipes wizard — for example, when you need to script peer creation
+across many databases or run the migration entirely inside your own network.
+PeerDB doesn't migrate indexes, constraints, or triggers automatically; you
+recreate those on the target after the data lands.
+
+## pg_dump and pg_restore {#pg-dump-pg-restore}
+
+[pg_dump and pg_restore](/cloud/managed-postgres/migrations/pg_dump-pg_restore)
+take a snapshot of the source and replay it on the target. There's no ongoing
+replication, so writes must stop on the source for the duration of the dump
+and restore. This is the right choice for small or static datasets, or
+non-production environments where a maintenance window is acceptable.
+
+## Logical replication {#logical-replication}
+
+[Logical replication](/cloud/managed-postgres/migrations/logical-replication)
+uses native Postgres publications and subscriptions to stream changes from
+the source to the target. You configure `wal_level`, replication slots, and
+the `REPLICATION` privilege yourself — no third-party tooling sits in the
+middle. Pick this path when you want full control over the replication
+mechanics or your environment rules out external migration tools.
+
+## After the migration {#after-migration}
+
+Once data is moving, use [data validation](/cloud/managed-postgres/migrations/data-validation)
+to confirm row counts and content match between source and target before
+cutting over application traffic. The [migrations FAQ](/cloud/managed-postgres/migrations/faq)
+covers common errors and recovery steps.

docs/cloud/managed-postgres/quickstart.md

@@ -259,7 +259,7 @@ The replication process will start, and you will be taken to the integration ove
 
 ### Query ClickHouse from Postgres {#pg-clickhouse-extension}
 
-The `pg_clickhouse` extension lets you query ClickHouse data directly from Postgres using standard SQL. This means your application can use Postgres as a unified query layer for both transactional and analytical data. See the [full documentation](/integrations/pg_clickhouse) for details.
+The `pg_clickhouse` extension lets you query ClickHouse data directly from Postgres using standard SQL. This means your application can use Postgres as a unified query layer for both transactional and analytical data. See the [full documentation](/cloud/managed-postgres/extensions/pg_clickhouse) for details.
 
 Enable the extension:
 

sidebars.js

@@ -337,49 +337,73 @@ const sidebars = {
       className: 'top-nav-item',
       link: { type: 'doc', id: 'cloud/managed-postgres/overview' },
       items: [
+        // Get started
         'cloud/managed-postgres/overview',
         'cloud/managed-postgres/quickstart',
         'cloud/managed-postgres/pricing',
         'cloud/managed-postgres/connection',
+        {
+          type: 'category',
+          label: 'Data migration',
+          collapsed: true,
+          collapsible: true,
+          link: { type: 'doc', id: 'cloud/managed-postgres/migrations/overview' },
+          items: [
+            'cloud/managed-postgres/migrations/clickpipes',
+            'cloud/managed-postgres/migrations/peerdb',
+            'cloud/managed-postgres/migrations/pg_dump-pg_restore',
+            'cloud/managed-postgres/migrations/logical-replication',
+            'cloud/managed-postgres/migrations/data-validation',
+            'cloud/managed-postgres/migrations/faq',
+          ],
+        },
+        // Use it
         'cloud/managed-postgres/clickhouse-integration',
         'cloud/managed-postgres/high-availability',
         'cloud/managed-postgres/read-replicas',
         'cloud/managed-postgres/scaling',
         'cloud/managed-postgres/backup-and-restore',
         'cloud/managed-postgres/security',
-        'cloud/managed-postgres/extensions',
+        // Configure
         'cloud/managed-postgres/settings',
+        {
+          type: 'category',
+          label: 'Extensions',
+          collapsed: false,
+          collapsible: true,
+          link: { type: 'doc', id: 'cloud/managed-postgres/extensions' },
+          items: [
+            {
+              type: 'category',
+              label: 'pg_clickhouse',
+              collapsed: true,
+              collapsible: true,
+              link: { type: 'doc', id: 'cloud/managed-postgres/extensions/pg_clickhouse/introduction' },
+              items: [
+                'cloud/managed-postgres/extensions/pg_clickhouse/tutorial',
+                'cloud/managed-postgres/extensions/pg_clickhouse/reference',
+              ],
+            },
+          ],
+        },
         'cloud/managed-postgres/upgrades',
-        'cloud/managed-postgres/benchmarks',
-        'cloud/managed-postgres/openapi',
+        // Operate & reference
         {
           type: 'category',
           label: 'Monitoring',
           collapsed: true,
           collapsible: true,
+          link: { type: 'doc', id: 'cloud/managed-postgres/monitoring/overview' },
           items: [
-            'cloud/managed-postgres/monitoring/overview',
             'cloud/managed-postgres/monitoring/dashboard',
             'cloud/managed-postgres/monitoring/query-insights',
             'cloud/managed-postgres/monitoring/prometheus',
             'cloud/managed-postgres/monitoring/metrics',
           ],
         },
+        'cloud/managed-postgres/benchmarks',
+        'cloud/managed-postgres/openapi',
         'cloud/managed-postgres/faq',
-        {
-          type: 'category',
-          label: 'Data migration',
-          collapsed: true,
-          collapsible: true,
-          items: [
-            'cloud/managed-postgres/migrations/clickpipes',
-            'cloud/managed-postgres/migrations/peerdb',
-            'cloud/managed-postgres/migrations/pg_dump-pg_restore',
-            'cloud/managed-postgres/migrations/logical-replication',
-            'cloud/managed-postgres/migrations/data-validation',
-            'cloud/managed-postgres/migrations/faq',
-          ],
-        },
       ],
     },
   ],
@@ -1219,18 +1243,6 @@ const sidebars = {
             'integrations/tools/data-integration/retool/index',
             'integrations/tools/data-integration/easypanel/index',
             'integrations/tools/data-integration/splunk/index',
-            {
-              type: 'category',
-              label: 'pg_clickhouse',
-              collapsed: true,
-              collapsible: true,
-              items: [
-                {
-                  type: 'autogenerated',
-                  dirName: 'integrations/tools/data-integration/pg_clickhouse',
-                },
-              ],
-            },
           ],
         },
         {