From c4288682525263e84e2280615a57fff58c6a4a98 Mon Sep 17 00:00:00 2001 From: Varjitt Jeeva Date: Tue, 19 Nov 2024 15:09:59 -0500 Subject: [PATCH] doc: format fix playbook sync steps (#624) --- docs/playbook.md | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/docs/playbook.md b/docs/playbook.md index 872b145..1092770 100644 --- a/docs/playbook.md +++ b/docs/playbook.md @@ -69,24 +69,24 @@ The `sync` command from Step 7 of the Quickstart guide does the following: If the `sync` command fails, you can try to run the individual commands that make up the `sync` command to see where the failure is. The individual commands are: -1. Syncing Sequences: +### 1. Syncing Sequences: - `sync-sequences` - reads and sets sequences values from SRC to DST at the time of command execution -2. Syncing Tables without Primary Keys: +### 2. Syncing Tables without Primary Keys: - `dump-tables` - dumps only tables without Primary Keys (to ensure only tables without Primary Keys are dumped, DO NOT specify the `--tables` flag for this command) - `load-tables` - load into DST DB the tables from the `dump-tables` command (found on disk) -3. Syncing NOT VALID Constraints: +### 3. Syncing NOT VALID Constraints: - `dump-schema` - dumps schema from your SRC DB schema onto disk (the files may already be on disk, but run this command just to ensure they exist anyways) - `load-constraints` - load NOT VALID constraints from disk (obtained by the `dump-schema` command) to your DST DB schema -4. Creating Indexes & Running ANALYZE: +### 4. Creating Indexes & Running ANALYZE: - `create-indexes` - Create indexes on the target database, and then runs ANALYZE as well. -5. Validating Data: +### 5. Validating Data: - `validate-data` - Check random 100 rows and last 100 rows of every table involved in the replication job, and ensure all match exactly.