From 7917c034e59ba6f0c2811ec49978cf231417cf13 Mon Sep 17 00:00:00 2001 From: Lev Kokotov Date: Thu, 13 Nov 2025 09:30:04 -0800 Subject: [PATCH] Update data-sync docs --- docs/features/sharding/resharding/hash.md | 9 ++++----- 1 file changed, 4 insertions(+), 5 deletions(-) diff --git a/docs/features/sharding/resharding/hash.md b/docs/features/sharding/resharding/hash.md index 06fd7fc..93904a3 100644 --- a/docs/features/sharding/resharding/hash.md +++ b/docs/features/sharding/resharding/hash.md @@ -20,10 +20,8 @@ PgDog has a command line interface you can call by running it directly: ```bash pgdog data-sync \ --from-database \ - --from-user \ --to-database \ - --to-user \ - --publication + --publication \ ``` Required (*) and optional parameters for this command are as follows: @@ -31,10 +29,11 @@ Required (*) and optional parameters for this command are as follows: | Option | Description | |-|-| | `--from-database`* | Name of the source database cluster. | -| `--from-user`* | Name of the user configured in `users.toml` for the source database cluster. | | `--to-database`* | Name of the destination database cluster. | -| `--to-user`* | Name of the user configured in `users.toml` for the destination database cluster. | | `--publication`* | Name of the Postgres [publication](schema.md#publication) for tables to be copied and sharded. It should exist on the **source** database. | +| `--replication-slot` | Name of the replication slot to use (and create if it doesn't exist) for syncing real-time changes. | +| `--replicate-only` | Don't copy data, just stream changes from the replication slot. | +| `--sync-only` | Perform the initial data sync only and exit. | ## How it works