1
.\" Title: \fBmysqldump\fR
3
.\" Generator: DocBook XSL Stylesheets v1.70.1 <http://docbook.sf.net/>
5
.\" Manual: MySQL Database System
8
.TH "\fBMYSQLDUMP\fR" "1" "01/09/2007" "MySQL 5.0" "MySQL Database System"
9
.\" disable hyphenation
11
.\" disable justification (adjust text to left margin only)
14
mysqldump \- a database backup program
17
\fBmysqldump [\fR\fB\fIoptions\fR\fR\fB] [\fR\fB\fIdb_name\fR\fR\fB [\fR\fB\fItbl_name\fR\fR\fB ...]]\fR
22
client is a backup program originally written by Igor Romanenko. It can be used to dump a database or a collection of databases for backup or transfer to another SQL server (not necessarily a MySQL server). The dump typically contains SQL statements to create the table, populate it, or both. However,
24
can also be used to generate files in CSV, other delimited text, or XML format.
26
If you are doing a backup on the server and your tables all are
28
tables, consider using the
30
instead because it can accomplish faster backups and faster restores. See
31
\fBmysqlhotcopy\fR(1).
33
There are three general ways to invoke
38
shell> \fBmysqldump [\fR\fB\fIoptions\fR\fR\fB] \fR\fB\fIdb_name\fR\fR\fB [\fR\fB\fItables\fR\fR\fB]\fR
39
shell> \fBmysqldump [\fR\fB\fIoptions\fR\fR\fB] \-\-databases \fR\fB\fIdb_name1\fR\fR\fB [\fR\fB\fIdb_name2\fR\fR\fB \fR\fB\fIdb_name3\fR\fR\fB...]\fR
40
shell> \fBmysqldump [\fR\fB\fIoptions\fR\fR\fB] \-\-all\-databases\fR
44
If you do not name any tables following
49
\fB\-\-all\-databases\fR
50
option, entire databases are dumped.
52
To get a list of the options your version of
55
\fBmysqldump \-\-help\fR.
59
options are shorthand for groups of other options.
63
fall into this category. For example, use of
65
is the same as specifying
66
\fB\-\-add\-drop\-table \-\-add\-locks \-\-create\-options \-\-disable\-keys \-\-extended\-insert \-\-lock\-tables \-\-quick \-\-set\-charset\fR. Note that all of the options that
68
stands for also are on by default because
72
To reverse the effect of a group option, uses its
73
\fB\-\-skip\-\fR\fB\fIxxx\fR\fR
74
form (\fB\-\-skip\-opt\fR
76
\fB\-\-skip\-compact\fR). It is also possible to select only part of the effect of a group option by following it with options that enable or disable specific features. Here are some examples:
79
To select the effect of
81
except for some features, use the
83
option for each feature. For example, to disable extended inserts and memory buffering, use
84
\fB\-\-opt \-\-skip\-extended\-insert \-\-skip\-quick\fR. (As of MySQL 5.0,
85
\fB\-\-skip\-extended\-insert \-\-skip\-quick\fR
93
for all features except index disabling and table locking, use
94
\fB\-\-skip\-opt \-\-disable\-keys \-\-lock\-tables\fR.
98
When you selectively enable or disable the effect of a group option, order is important because options are processed first to last. For example,
99
\fB\-\-disable\-keys \-\-lock\-tables \-\-skip\-opt\fR
100
would not have the intended effect; it is the same as
105
can retrieve and dump table contents row by row, or it can retrieve the entire content from a table and buffer it in memory before dumping it. Buffering in memory can be a problem if you are dumping large tables. To dump tables row by row, use the
108
\fB\-\-opt\fR, which enables
112
\fB\-\-quick\fR) is enabled by default as of MySQL 5.0 to enable memory buffering, use
113
\fB\-\-skip\-quick\fR.
115
If you are using a recent version of
117
to generate a dump to be reloaded into a very old MySQL server, you should not use the
120
\fB\-\-extended\-insert\fR
126
supports the following options:
132
Display a help message and exit.
135
\fB\-\-add\-drop\-database\fR
139
statement before each
144
\fB\-\-add\-drop\-table\fR
148
statement before each
155
Surround each table dump with
159
statements. This results in faster inserts when the dump file is reloaded. See
160
Section\ 2.16, \(lqSpeed of INSERT Statements\(rq.
163
\fB\-\-all\-databases\fR,
166
Dump all tables in all databases. This is the same as using the
168
option and naming all the databases on the command line.
171
\fB\-\-allow\-keywords\fR
173
Allow creation of column names that are keywords. This works by prefixing each column name with the table name.
176
\fB\-\-character\-sets\-dir=\fR\fB\fIpath\fR\fR
178
The directory where character sets are installed. See
179
Section\ 9.1, \(lqThe Character Set Used for Data and Sorting\(rq.
185
Write additional information in the dump file such as program version, server version, and host. This option is enabled by default. To suppress this additional information, use
186
\fB\-\-skip\-comments\fR.
191
Produce less verbose output. This option suppresses comments and enables the
192
\fB\-\-skip\-add\-drop\-table\fR,
193
\fB\-\-no\-set\-names\fR,
194
\fB\-\-skip\-disable\-keys\fR, and
195
\fB\-\-skip\-add\-locks\fR
199
\fB\-\-compatible=\fR\fB\fIname\fR\fR
201
Produce output that is more compatible with other database systems or with older MySQL servers. The value of
214
no_field_options. To use several values, separate them by commas. These values have the same meaning as the corresponding options for setting the server SQL mode. See
215
the section called \(lqSQL MODES\(rq.
217
This option does not guarantee compatibility with other servers. It only enables those SQL mode values that are currently available for making dump output more compatible. For example,
218
\fB\-\-compatible=oracle\fR
219
does not map data types to Oracle types or use Oracle comment syntax.
222
\fB\-\-complete\-insert\fR,
227
statements that include column names.
233
Compress all information sent between the client and the server if both support compression.
236
\fB\-\-create\-options\fR
238
Include all MySQL\-specific table options in the
246
Dump several databases. Normally,
248
treats the first name argument on the command line as a database name and following names as table names. With this option, it treats all name arguments as database names.
252
statements are included in the output before each new database.
255
\fB\-\-debug[=\fR\fB\fIdebug_options\fR\fR\fB]\fR,
256
\fB\-# [\fR\fB\fIdebug_options\fR\fR\fB]\fR
258
Write a debugging log. The
261
\'d:t:o,\fIfile_name\fR'. The default value is
262
\'d:t:o,/tmp/mysqldump.trace'.
265
\fB\-\-default\-character\-set=\fR\fB\fIcharset_name\fR\fR
269
as the default character set. See
270
Section\ 9.1, \(lqThe Character Set Used for Data and Sorting\(rq. If no character set is specified,
276
\fB\-\-delayed\-insert\fR
280
statements rather than
285
\fB\-\-delete\-master\-logs\fR
287
On a master replication server, delete the binary logs after performing the dump operation. This option automatically enables
288
\fB\-\-master\-data\fR.
291
\fB\-\-disable\-keys\fR,
294
For each table, surround the
297
/*!40000 ALTER TABLE \fItbl_name\fR DISABLE KEYS */;
299
/*!40000 ALTER TABLE \fItbl_name\fR ENABLE KEYS */;
300
statements. This makes loading the dump file faster because the indexes are created after all rows are inserted. This option is effective for
305
\fB\-\-extended\-insert\fR,
310
syntax that include several
312
lists. This results in a smaller dump file and speeds up inserts when the file is reloaded.
315
\fB\-\-fields\-terminated\-by=...\fR,
316
\fB\-\-fields\-enclosed\-by=...\fR,
317
\fB\-\-fields\-optionally\-enclosed\-by=...\fR,
318
\fB\-\-fields\-escaped\-by=...\fR
320
These options are used with the
322
option and have the same meaning as the corresponding clauses for
323
LOAD DATA INFILE. See
324
Section\ 2.5, \(lqLOAD DATA INFILE Syntax\(rq.
327
\fB\-\-first\-slave\fR,
330
Deprecated. Now renamed to
331
\fB\-\-lock\-all\-tables\fR.
334
\fB\-\-flush\-logs\fR,
337
Flush the MySQL server log files before starting the dump. This option requires the
339
privilege. Note that if you use this option in combination with the
340
\fB\-\-all\-databases\fR
342
\fB\-A\fR) option, the logs are flushed
343
\fIfor each database dumped\fR. The exception is when using
344
\fB\-\-lock\-all\-tables\fR
346
\fB\-\-master\-data\fR: In this case, the logs are flushed only once, corresponding to the moment that all tables are locked. If you want your dump and the log flush to happen at exactly the same moment, you should use
347
\fB\-\-flush\-logs\fR
349
\fB\-\-lock\-all\-tables\fR
351
\fB\-\-master\-data\fR.
354
\fB\-\-flush\-privileges\fR
358
statement after dumping the
360
database. This option should be used any time the dump contains the
362
database and any other database that depends on the data in the
364
database for proper restoration. This option was added in MySQL 5.0.26.
370
Continue even if an SQL error occurs during a table dump.
372
One use for this option is to cause
374
to continue executing even when it encounters a view that has become invalid because the defintion refers to a table that has been dropped. Without
377
exits with an error message. With
380
prints the error message, but it also writes a SQL comment containing the view definition to the dump output and continues executing.
383
\fB\-\-host=\fR\fB\fIhost_name\fR\fR,
384
\fB\-h \fR\fB\fIhost_name\fR\fR
386
Dump data from the MySQL server on the given host. The default host is
392
Dump binary columns using hexadecimal notation (for example,
395
0x616263). The affected data types are
398
BLOB. As of MySQL 5.0.13,
400
columns are affected as well.
403
\fB\-\-ignore\-table=\fR\fB\fIdb_name.tbl_name\fR\fR
405
Do not dump the given table, which must be specified using both the database and table names. To ignore multiple tables, use this option multiple times.
408
\fB\-\-insert\-ignore\fR
417
\fB\-\-lines\-terminated\-by=...\fR
419
This option is used with the
421
option and has the same meaning as the corresponding clause for
422
LOAD DATA INFILE. See
423
Section\ 2.5, \(lqLOAD DATA INFILE Syntax\(rq.
426
\fB\-\-lock\-all\-tables\fR,
429
Lock all tables across all databases. This is achieved by acquiring a global read lock for the duration of the whole dump. This option automatically turns off
430
\fB\-\-single\-transaction\fR
432
\fB\-\-lock\-tables\fR.
435
\fB\-\-lock\-tables\fR,
438
Lock all tables before dumping them. The tables are locked with
440
to allow concurrent inserts in the case of
442
tables. For transactional tables such as
446
\fB\-\-single\-transaction\fR
447
is a much better option, because it does not need to lock the tables at all.
449
Please note that when dumping multiple databases,
450
\fB\-\-lock\-tables\fR
451
locks tables for each database separately. Therefore, this option does not guarantee that the tables in the dump file are logically consistent between databases. Tables in different databases may be dumped in completely different states.
454
\fB\-\-master\-data[=\fR\fB\fIvalue\fR\fR\fB]\fR
456
Write the binary log filename and position to the output. This option requires the
458
privilege and the binary log must be enabled. If the option value is equal to 1, the position and filename are written to the dump output in the form of a
460
statement. If the dump is from a master server and you use it to set up a slave server, the
462
statement causes the slave to start from the correct position in the master's binary logs. If the option value is equal to 2, the
464
statement is written as an SQL comment. (This is the default action if
469
\fB\-\-master\-data\fR
470
option automatically turns off
471
\fB\-\-lock\-tables\fR. It also turns on
472
\fB\-\-lock\-all\-tables\fR, unless
473
\fB\-\-single\-transaction\fR
474
also is specified (in which case, a global read lock is acquired only for a short time at the beginning of the dump. See also the description for
475
\fB\-\-single\-transaction\fR. In all cases, any action on logs happens at the exact moment of the dump.
478
\fB\-\-no\-autocommit\fR
482
statements for each dumped table within
489
\fB\-\-no\-create\-db\fR,
492
This option suppresses the
494
statements that are otherwise included in the output if the
497
\fB\-\-all\-databases\fR
501
\fB\-\-no\-create\-info\fR,
506
statements that re\-create each dumped table.
512
Do not write any table row information (that is, do not dump table contents). This is very useful if you want to dump only the
514
statement for the table.
519
This option is shorthand; it is the same as specifying
520
\fB\-\-add\-drop\-table \-\-add\-locks \-\-create\-options \-\-disable\-keys \-\-extended\-insert \-\-lock\-tables \-\-quick \-\-set\-charset\fR. It should give you a fast dump operation and produce a dump file that can be reloaded into a MySQL server quickly.
522
\fIThe \fR\fI\fB\-\-opt\fR\fR\fI option is enabled by default. Use \fR\fI\fB\-\-skip\-opt\fR\fR\fI to disable it.\fR
523
See the discussion at the beginning of this section for information about selectively enabling or disabling certain of the options affected by
527
\fB\-\-order\-by\-primary\fR
529
Sorts each table's rows by its primary key, or by its first unique index, if such an index exists. This is useful when dumping a
531
table to be loaded into an
533
table, but will make the dump itself take considerably longer.
536
\fB\-\-password[=\fR\fB\fIpassword\fR\fR\fB]\fR,
537
\fB\-p[\fR\fB\fIpassword\fR\fR\fB]\fR
539
The password to use when connecting to the server. If you use the short option form (\fB\-p\fR), you
541
have a space between the option and the password. If you omit the
547
option on the command line, you are prompted for one.
549
Specifying a password on the command line should be considered insecure. See
550
Section\ 7.6, \(lqKeeping Your Password Secure\(rq.
553
\fB\-\-port=\fR\fB\fIport_num\fR\fR,
554
\fB\-P \fR\fB\fIport_num\fR\fR
556
The TCP/IP port number to use for the connection.
559
\fB\-\-protocol={TCP|SOCKET|PIPE|MEMORY}\fR
561
The connection protocol to use.
567
This option is useful for dumping large tables. It forces
569
to retrieve rows for a table from the server a row at a time rather than retrieving the entire row set and buffering it in memory before writing it out.
572
\fB\-\-quote\-names\fR,
575
Quote database, table, and column names within \(oq`\(cq characters. If the
577
SQL mode is enabled, names are quoted within \(oq"\(cq characters. This option is enabled by default. It can be disabled with
578
\fB\-\-skip\-quote\-names\fR, but this option should be given after any option such as
581
\fB\-\-quote\-names\fR.
584
\fB\-\-result\-file=\fR\fB\fIfile\fR\fR,
585
\fB\-r \fR\fB\fIfile\fR\fR
587
Direct output to a given file. This option should be used on Windows to prevent newline \(oq\\n\(cq characters from being converted to \(oq\\r\\n\(cq carriage return/newline sequences. The result file is created and its contents overwritten, even if an error occurs while generating the dump. The previous contents are lost.
593
Dump stored routines (functions and procedures) from the dumped databases. Use of this option requires the
597
table. The output generated by using
603
statements to re\-create the routines. However, these statements do not include attributes such as the routine creation and modification timestamps. This means that when the routines are reloaded, they will be created with the timestamps equal to the reload time.
605
If you require routines to be re\-created with their original timestamp attributes, do not use
606
\fB\-\-routines\fR. Instead, dump and reload the contents of the
608
table directly, using a MySQL account that has appropriate privileges for the
612
This option was added in MySQL 5.0.13. Before that, stored routines are not dumped. Routine
614
values are not dumped until MySQL 5.0.20. This means that before 5.0.20, when routines are reloaded, they will be created with the definer set to the reloading user. If you require routines to be re\-created with their original definer, dump and load the contents of the
616
table directly as described earlier.
619
\fB\-\-set\-charset\fR
622
SET NAMES \fIdefault_character_set\fR
623
to the output. This option is enabled by default. To suppress the
626
\fB\-\-skip\-set\-charset\fR.
629
\fB\-\-single\-transaction\fR
633
SQL statement before dumping data from the server. It is useful only with transactional tables such as
636
BDB, because then it dumps the consistent state of the database at the time when
638
was issued without blocking any applications.
640
When using this option, you should keep in mind that only
642
tables are dumped in a consistent state. For example, any
646
tables dumped while using this option may still change state.
649
\fB\-\-single\-transaction\fR
651
\fB\-\-lock\-tables\fR
652
option are mutually exclusive, because
654
causes any pending transactions to be committed implicitly.
656
This option is not supported for MySQL Cluster tables; the results cannot be guaranteed to be consistent due to the fact that the
658
storage engine supports only the
660
transaction isolation level. You should always use
662
backup and restore instead.
664
To dump large tables, you should combine this option with
670
See the description for the
675
\fB\-\-socket=\fR\fB\fIpath\fR\fR,
676
\fB\-S \fR\fB\fIpath\fR\fR
679
localhost, the Unix socket file to use, or, on Windows, the name of the named pipe to use.
682
\fB\-\-skip\-comments\fR
684
See the description for the
691
Options that begin with
693
specify whether to connect to the server via SSL and indicate where to find SSL keys and certificates. See
694
Section\ 7.7.3, \(lqSSL Command Options\(rq.
697
\fB\-\-tab=\fR\fB\fIpath\fR\fR,
698
\fB\-T \fR\fB\fIpath\fR\fR
700
Produce tab\-separated data files. For each dumped table,
703
\fI\fItbl_name\fR\fR\fI.sql\fR
704
file that contains the
706
statement that creates the table, and a
707
\fI\fItbl_name\fR\fR\fI.txt\fR
708
file that contains its data. The option value is the directory in which to write the files.
712
data files are formatted using tab characters between column values and a newline at the end of each line. The format can be specified explicitly using the
713
\fB\-\-fields\-\fR\fB\fIxxx\fR\fR
715
\fB\-\-lines\-terminated\-by\fR
718
\fBNote\fR: This option should be used only when
720
is run on the same machine as the
722
server. You must have the
724
privilege, and the server must have permission to write files in the directory that you specify.
735
regards all name arguments following the option as table names.
740
Dump triggers for each dumped table. This option is enabled by default; disable it with
741
\fB\-\-skip\-triggers\fR. This option was added in MySQL 5.0.11. Before that, triggers are not dumped.
747
SET TIME_ZONE='+00:00'
748
to the dump file so that
750
columns can be dumped and reloaded between servers in different time zones. Without this option,
752
columns are dumped and reloaded in the time zones local to the source and destination servers, which can cause the values to change.
754
also protects against changes due to daylight saving time.
756
is enabled by default. To disable it, use
757
\fB\-\-skip\-tz\-utc\fR. This option was added in MySQL 5.0.15.
760
\fB\-\-user=\fR\fB\fIuser_name\fR\fR,
761
\fB\-u \fR\fB\fIuser_name\fR\fR
763
The MySQL username to use when connecting to the server.
769
Verbose mode. Print more information about what the program does.
775
Display version information and exit.
778
\fB\-\-where='\fR\fB\fIwhere_condition\fR\fR\fB'\fR,
779
\fB\-w '\fR\fB\fIwhere_condition\fR\fR\fB'\fR
781
Dump only rows selected by the given
783
condition. Quotes around the condition are mandatory if it contains spaces or other characters that are special to your command interpreter.
789
\-\-where="user='jimf'"
799
Write dump output as well\-formed XML.
801
\fBNULL\fR\fB, \fR\fB'NULL'\fR\fB, and Empty Values\fR: For some column named
802
\fIcolumn_name\fR, the
804
value, an empty string, and the string value
806
are distinguished from one another in the output generated by this option as follows:
816
\fBXML Representation\fR:
819
NULL (\fIunknown value\fR)
821
<field name="\fIcolumn_name\fR"
825
\'' (\fIempty string\fR)
828
name="\fIcolumn_name\fR"></field>
831
\'NULL' (\fIstring value\fR)
834
name="\fIcolumn_name\fR">NULL</field>
838
Beginning with MySQL 5.0.26, the output from the
840
client when run using the
842
option also follows these rules. (See
843
the section called \(lq\fBMYSQL\fR OPTIONS\(rq.)
847
You can also set the following variables by using
848
\fB\-\-\fR\fB\fIvar_name\fR\fR\fB=\fR\fB\fIvalue\fR\fR
854
The maximum size of the buffer for client/server communication. The maximum is 1GB.
859
The initial size of the buffer for client/server communication. When creating multiple\-row\-insert statements (as with option
860
\fB\-\-extended\-insert\fR
866
length. If you increase this variable, you should also ensure that the
868
variable in the MySQL server is at least this large.
872
It is also possible to set variables by using
873
\fB\-\-set\-variable=\fR\fB\fIvar_name\fR\fR\fB=\fR\fB\fIvalue\fR\fR
875
\fB\-O \fR\fB\fIvar_name\fR\fR\fB=\fR\fB\fIvalue\fR\fR
877
\fIThis syntax is deprecated\fR.
879
The most common use of
881
is probably for making a backup of an entire database:
885
shell> \fBmysqldump \fR\fB\fIdb_name\fR\fR\fB > \fR\fB\fIbackup\-file.sql\fR\fR
889
You can read the dump file back into the server like this:
893
shell> \fBmysql \fR\fB\fIdb_name\fR\fR\fB < \fR\fB\fIbackup\-file.sql\fR\fR
901
shell> \fBmysql \-e "source \fR\fB\fI/path\-to\-backup/backup\-file.sql\fR\fR\fB" \fR\fB\fIdb_name\fR\fR
906
is also very useful for populating databases by copying data from one MySQL server to another:
910
shell> \fBmysqldump \-\-opt \fR\fB\fIdb_name\fR\fR\fB | mysql \-\-host=\fR\fB\fIremote_host\fR\fR\fB \-C \fR\fB\fIdb_name\fR\fR
914
It is possible to dump several databases with one command:
918
shell> \fBmysqldump \-\-databases \fR\fB\fIdb_name1\fR\fR\fB [\fR\fB\fIdb_name2\fR\fR\fB ...] > my_databases.sql\fR
922
To dump all databases, use the
923
\fB\-\-all\-databases\fR
928
shell> \fBmysqldump \-\-all\-databases > all_databases.sql\fR
936
provides a way of making an online backup:
940
shell> \fBmysqldump \-\-all\-databases \-\-single\-transaction > all_databases.sql\fR
944
This backup just needs to acquire a global read lock on all tables (using
945
FLUSH TABLES WITH READ LOCK) at the beginning of the dump. As soon as this lock has been acquired, the binary log coordinates are read and the lock is released. If and only if one long updating statement is running when the
947
statement is issued, the MySQL server may get stalled until that long statement finishes, and then the dump becomes lock\-free. If the update statements that the MySQL server receives are short (in terms of execution time), the initial lock period should not be noticeable, even with many updates.
949
For point\-in\-time recovery (also known as
950
\(lqroll\-forward,\(rq
951
when you need to restore an old backup and replay the changes that happened since that backup), it is often useful to rotate the binary log (see
952
Section\ 10.3, \(lqThe Binary Log\(rq) or at least know the binary log coordinates to which the dump corresponds:
956
shell> \fBmysqldump \-\-all\-databases \-\-master\-data=2 > all_databases.sql\fR
964
shell> \fBmysqldump \-\-all\-databases \-\-flush\-logs \-\-master\-data=2\fR
965
\fB> all_databases.sql\fR
970
\fB\-\-master\-data\fR
972
\fB\-\-single\-transaction\fR
973
options can be used simultaneously, which provides a convenient way to make an online backup suitable for point\-in\-time recovery if tables are stored using the
977
For more information on making backups, see
978
Section\ 8.1, \(lqDatabase Backups\(rq, and
979
Section\ 8.2, \(lqExample Backup and Recovery Strategy\(rq.
981
If you encounter problems backing up views, please read the section that covers restrictions on views which describes a workaround for backing up views when this fails due to insufficient privileges. See
982
Section\ 4, \(lqRestrictions on Views\(rq.
985
Copyright 1997\-2006 MySQL AB
987
This documentation is NOT distributed under a GPL license. Use of this documentation is subject to the following terms: You may create a printed copy of this documentation solely for your own personal use. Conversion to other formats is allowed as long as the actual content is not altered or edited in any way. You shall not publish or distribute this documentation in any form or on any media, except if you distribute the documentation in a manner similar to how MySQL disseminates it (that is, electronically for download on a Web site with the software) or on a CD\-ROM or similar medium, provided however that the documentation is disseminated together with the software on the same medium. Any other use, such as any dissemination of printed copies or use of this documentation, in whole or in part, in another publication, requires the prior written consent from an authorized representative of MySQL AB. MySQL AB reserves any and all rights to this documentation not expressly granted above.
991
for more information.
994
my_print_defaults(1),
1002
mysql_explain_log(1),
1003
mysql_fix_privilege_tables(1),
1004
mysql_tzinfo_to_sql(1),
1022
For more information, please refer to the MySQL Reference Manual,
1023
which may already be installed locally and which is also available
1024
online at http://dev.mysql.com/doc/.
1026
MySQL AB (http://www.mysql.com/).
1027
This software comes with no warranty.
added
removed
man/mysqldump.1
