pg_dump

Author: levkk

docs/features/sharding/resharding/schema.md

@@ -3,7 +3,7 @@ icon: material/database-edit-outline
 ---
 # Schema sync
 
-PgDog can copy tables, indexes and other entities from your production database to the new, sharded database automatically. This is faster than using `pg_dump`, because we separate this process into two parts:
+PgDog can copy tables, indices and other entities from your production database to the new, sharded database automatically. This is faster than using `pg_dump`, because we separate this process into two parts:
 
 1. [Create tables](#tables-and-primary-keys), primary key indices, and sequences
 2. Create [secondary indices](#secondary-indices)
@@ -34,7 +34,7 @@ Required (*) and optional parameters for this command are as follows:
 
 ## Tables and primary keys
 
-The first step in the schema sync copies over tables and their primary key indexes from the source database to the new, resharded cluster. This has to be done separately, because Postgres's logical replication only copies data and doesn't manage table schemas.
+The first step in the schema sync copies over tables and their primary key indices from the source database to the new, resharded cluster. This has to be done separately, because Postgres's logical replication only copies data and doesn't manage table schemas.
 
 ### Primary keys
 
@@ -72,6 +72,17 @@ schema_admin = true
 
 PgDog will use that user to connect to the source and destination databases, so make sure to specify one for both of them.
 
+### `pg_dump` version
+
+PgDog is using `pg_dump` under the hood to export schema definitions. Postgres requires the version of `pg_dump` and the server to be identical. Our [Docker image](../../../installation.md) comes with `pg_dump` for PostgreSQL 16, but your database server may run a different version.
+
+Before proceeding, make sure to install the correct version of `pg_dump` for your source database. If you have multiple versions of `pg_dump` installed on the same host, you can specify the path to the right one in `pgdog.toml`:
+
+```toml
+[replication]
+pg_dump_path = "/path/to/pg_dump"
+```
+
 ## Secondary indices
 
-This step is performed after [data sync](hash.md) is complete. Running this step will create secondary indexes on all your tables, which will take some time.
+This step is performed after [data sync](hash.md) is complete. Running this step will create secondary indices on all your tables, which will take some time.