From 09658d96a739e55652290bb8d88d7a388b18fa05 Mon Sep 17 00:00:00 2001
From: Lisa Owen
Date: Thu, 21 Dec 2017 14:43:41 -0700
Subject: [PATCH] docs - correct the gptransfer example using --full and -d
options together (#4168)
* docs - correct the example using --full and -d options
* avoid using --full and --schema-only together, do not prohibit
* clean up schema copy bullet point
---
gpdb-doc/dita/best_practices/gptransfer.xml | 11 +++++------
1 file changed, 5 insertions(+), 6 deletions(-)
diff --git a/gpdb-doc/dita/best_practices/gptransfer.xml b/gpdb-doc/dita/best_practices/gptransfer.xml
index 450baca18b..144f938fe6 100644
--- a/gpdb-doc/dita/best_practices/gptransfer.xml
+++ b/gpdb-doc/dita/best_practices/gptransfer.xml
@@ -232,9 +232,9 @@ host2_name,host2_ipaddr
The --full option and the --schema-only option can be
used together if you want to copy a database in phases, for example, during scheduled
- periods of downtime or low activity. Run gptransfer --full --schema-only -d
- <database_name> ... to create the full database on the destination
- cluster, but with no data. Then you can transfer the tables in stages during scheduled down
+ periods of downtime or low activity. Run gptransfer --full --schema-only ...
+ to create the full database schema on the destination
+ cluster, but with no data. You can then transfer the tables in stages during scheduled down
times or periods of low activity. Be sure to include the --truncate or
--drop option when you later transfer tables to prevent the transfer from
failing because the table already exists at the destination.
@@ -281,9 +281,8 @@ host2_name,host2_ipaddr
smaller tables.
- Before you begin to transfer data, replicate the schema or schemas from the source
- cluster to the destination cluster. Do not use gptransfer with the
- --full –schema-only options. Here are some options for copying the
- schema:
+ cluster to the destination cluster. Options for copying the
+ schema include:
- Use the gpsd (Greenplum Statistics Dump) support utility. This
method includes statistics, so be sure to run ANALYZE after creating
the schema on the destination cluster.
--
GitLab