You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: doc/command-line-flags.md
+16Lines changed: 16 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -111,6 +111,14 @@ While the ongoing estimated number of rows is still heuristic, it's almost exact
111
111
112
112
Without this parameter, migration is a _noop_: testing table creation and validity of migration, but not touching data.
113
113
114
+
### force-named-cut-over
115
+
116
+
If given, a `cut-over` command must name the migrated table, or else ignored.
117
+
118
+
### force-named-panic
119
+
120
+
If given, a `panic` command must name the migrated table, or else ignored.
121
+
114
122
### force-table-names
115
123
116
124
Table name prefix to be used on the temporary tables.
@@ -193,6 +201,14 @@ Allows `gh-ost` to connect to the MySQL servers using encrypted connections, but
193
201
194
202
`--ssl-ca=/path/to/ca-cert.pem`: ca certificate file (in PEM format) to use for server certificate verification. If specified, the default system ca cert pool will not be used for verification, only the ca cert provided here. Requires `--ssl`.
195
203
204
+
### ssl-cert
205
+
206
+
`--ssl-cert=/path/to/ssl-cert.crt`: SSL public key certificate file (in PEM format).
207
+
208
+
### ssl-key
209
+
210
+
`--ssl-key=/path/to/ssl-key.key`: SSL private key file (in PEM format).
211
+
196
212
### test-on-replica
197
213
198
214
Issue the migration on a replica; do not modify data on master. Useful for validating, testing and benchmarking. See [`testing-on-replica`](testing-on-replica.md)
Copy file name to clipboardExpand all lines: go/cmd/gh-ost/main.go
+9Lines changed: 9 additions & 0 deletions
Original file line number
Diff line number
Diff line change
@@ -57,6 +57,8 @@ func main() {
57
57
58
58
flag.BoolVar(&migrationContext.UseTLS, "ssl", false, "Enable SSL encrypted connections to MySQL hosts")
59
59
flag.StringVar(&migrationContext.TLSCACertificate, "ssl-ca", "", "CA certificate in PEM format for TLS connections to MySQL hosts. Requires --ssl")
60
+
flag.StringVar(&migrationContext.TLSCertificate, "ssl-cert", "", "Certificate in PEM format for TLS connections to MySQL hosts. Requires --ssl")
61
+
flag.StringVar(&migrationContext.TLSKey, "ssl-key", "", "Key in PEM format for TLS connections to MySQL hosts. Requires --ssl")
60
62
flag.BoolVar(&migrationContext.TLSAllowInsecure, "ssl-allow-insecure", false, "Skips verification of MySQL hosts' certificate chain and host name. Requires --ssl")
61
63
62
64
flag.StringVar(&migrationContext.DatabaseName, "database", "", "database name (mandatory)")
@@ -87,6 +89,7 @@ func main() {
87
89
flag.BoolVar(&migrationContext.TimestampOldTable, "timestamp-old-table", false, "Use a timestamp in old table name. This makes old table names unique and non conflicting cross migrations")
88
90
cutOver:=flag.String("cut-over", "atomic", "choose cut-over type (default|atomic, two-step)")
89
91
flag.BoolVar(&migrationContext.ForceNamedCutOverCommand, "force-named-cut-over", false, "When true, the 'unpostpone|cut-over' interactive command must name the migrated table")
92
+
flag.BoolVar(&migrationContext.ForceNamedPanicCommand, "force-named-panic", false, "When true, the 'panic' interactive command must name the migrated table")
90
93
91
94
flag.BoolVar(&migrationContext.SwitchToRowBinlogFormat, "switch-to-rbr", false, "let this tool automatically switch binary log format to 'ROW' on the replica, if needed. The format will NOT be switched back. I'm too scared to do that, and wish to protect you if you happen to execute another migration while this one is running")
92
95
flag.BoolVar(&migrationContext.AssumeRBR, "assume-rbr", false, "set to 'true' when you know for certain your server uses 'ROW' binlog_format. gh-ost is unable to tell, event after reading binlog_format, whether the replication process does indeed use 'ROW', and restarts replication to be certain RBR setting is applied. Such operation requires SUPER privileges which you might not have. Setting this flag avoids restarting replication and you can proceed to use gh-ost without SUPER privileges")
0 commit comments