2009-09-16 14:03:18 +02:00
'\" t
2009-05-25 11:59:47 +02:00
. \"
2024-10-08 14:05:12 +02:00
.TH "\fBMARIADB-DUMP\fR" "1" "8 October 2024" "MariaDB 11.6" "MariaDB Database System"
2009-09-16 14:03:18 +02:00
. \" -----------------------------------------------------------------
. \" * set default formatting
. \" -----------------------------------------------------------------
2009-05-25 11:59:47 +02:00
. \" disable hyphenation
.nh
. \" disable justification (adjust text to left margin only)
.ad l
2009-09-16 14:03:18 +02:00
. \" -----------------------------------------------------------------
. \" * MAIN CONTENT STARTS HERE *
. \" -----------------------------------------------------------------
2024-09-03 19:15:59 +02:00
. \" mariadb-dump
2009-09-16 14:03:18 +02:00
. \" dumping: databases and tables
. \" backups: databases and tables
. \" databases: dumping
. \" tables: dumping
2009-05-25 11:59:47 +02:00
.SH "NAME"
2024-09-03 19:15:59 +02:00
mariadb-dump \- a database backup program (mariadb-dump is now a symlink to mariadb-dump)
2009-05-25 11:59:47 +02:00
.SH "SYNOPSIS"
2024-09-03 19:15:59 +02:00
.HP \w '\fBmariadb-dump\ [\fR\fB\fIoptions\fR\fR\fB]\ [\fR\fB\fIdb_name\fR\fR\fB\ [\fR\fB\fItbl_name\fR\fR\fB\ \& .\&.\&.]]\fR\ 'u
\fB mariadb-dump [\fR \fB \fI options\fR \fR \fB ] [\fR \fB \fI db_name\fR \fR \fB [\fR \fB \fI tbl_name\fR \fR \fB \& .\& .\& .]]\fR
2009-05-25 11:59:47 +02:00
.SH "DESCRIPTION"
.PP
The
2024-09-03 19:15:59 +02:00
\fB mariadb-dump\fR
2015-09-09 14:32:52 +02:00
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 MariaDB server)\& . The dump typically contains SQL statements to create the table, populate it, or both\& . However,
2024-09-03 19:15:59 +02:00
\fB mariadb-dump\fR
2009-09-16 14:03:18 +02:00
can also be used to generate files in CSV, other delimited text, or XML format\& .
2009-05-25 11:59:47 +02:00
.PP
If you are doing a backup on the server and your tables all are
MyISAM
tables, consider using the
2024-09-03 19:15:59 +02:00
\fB mariadb-hotcopy\fR
2009-09-16 14:03:18 +02:00
instead because it can accomplish faster backups and faster restores\& . See
2024-09-03 19:15:59 +02:00
\fB mariadb-hotcopy\fR (1)\& .
2009-05-25 11:59:47 +02:00
.PP
2020-08-30 10:53:20 +10:00
There are four general ways to invoke
2024-09-03 19:15:59 +02:00
\fB mariadb-dump\fR :
2009-05-25 11:59:47 +02:00
.sp
2009-09-16 14:03:18 +02:00
.if n \{ \
.RS 4
. \}
2009-05-25 11:59:47 +02:00
.nf
2024-09-03 19:15:59 +02:00
shell> \fB mariadb-dump [\fR \fB \fI options\fR \fR \fB ] \fR \fB \fI db_name\fR \fR \fB [\fR \fB \fI tbl_name\fR \fR \fB \& .\& .\& .]\fR
shell> \fB mariadb-dump [\fR \fB \fI options\fR \fR \fB ] \- \- databases \fR \fB \fI db_name\fR \fR \fB \& .\& .\& .\fR
shell> \fB mariadb-dump [\fR \fB \fI options\fR \fR \fB ] \- \- all\- databases\fR
shell> \fB mariadb-dump [\fR \fB \fI options\fR \fR \fB ] \- \- system={options}\fR
2009-05-25 11:59:47 +02:00
.fi
2009-09-16 14:03:18 +02:00
.if n \{ \
2009-05-25 11:59:47 +02:00
.RE
2009-09-16 14:03:18 +02:00
. \}
2009-05-25 11:59:47 +02:00
.PP
If you do not name any tables following
\fI db_name\fR
or if you use the
\fB \- \- databases\fR
or
\fB \- \- all\- databases\fR
2009-09-16 14:03:18 +02:00
option, entire databases are dumped\& .
2009-05-25 11:59:47 +02:00
.PP
2024-09-03 19:15:59 +02:00
\fB mariadb-dump\fR
2009-05-25 11:59:47 +02:00
does not dump the
2015-09-09 14:32:52 +02:00
INFORMATION_SCHEMA or performance_schema
MDEV-23789: Fix unnecessary acute accents in man pages
The man pages has several places where \' is intended to escape the single
quote and just print '. However, in reality this will print an ` (acute
accent). Fix this by removing excess backslashes. Also remove some excess
& in front of dots, such escaping is also unnecessary.
Also join several lines to avoid lone words in quotes to be read by groff
as macros when they are just text.
In a table (t{}) the content must be on new lines separately, so groff
will try to read them as macros too, so use \(aq that renders to '
(single quote).
This error was originally detected by Lintian:
https://lintian.debian.org/tags/acute-accent-in-manual-page
Example of man page sections before and after:
Make a backup of each table´s data file using the name tbl_name.OLD.
->
Make a backup of each table's data file using the name tbl_name.OLD.
A typical debug_options string is ´d:t:o,file_name´.
The default is ´d:t:o,/tmp/my_print_defaults.trace´.
->
A typical debug_options string is 'd:t:o,file_name'.
The default is 'd:t:o,/tmp/my_print_defaults.trace'.
shell> mysql --xml -uroot -e "SHOW VARIABLES LIKE ´version%´"
<?xml version="1.0"?>
<resultset statement="SHOW VARIABLES LIKE ´version%´" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
->
shell> mysql --xml -uroot -e "SHOW VARIABLES LIKE 'version%'"
<?xml version="1.0"?>
<resultset statement="SHOW VARIABLES LIKE 'version%'" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
This command was used to validate no man pages have syntax errors:
for x in *.?
do
echo "##### $x #####"
LC_ALL=C.UTF-8 MANROFFSEQ='' MANWIDTH=80 man --warnings -E UTF-8 -l -Tutf8 -Z $x >/dev/null
done
The man pages are not perfect after this, there are still a lot of
suboptimal syntax, but this helps towards better man pages.
All new code of the whole pull request, including one or several files
that are either new files or modified ones, are contributed under the
BSD-new license. I am contributing on behalf of my employer Amazon Web
Services, Inc.
2023-03-11 13:01:39 -08:00
databases by default\& . To dump these,
2015-09-09 14:32:52 +02:00
name them explicitly on the command line, although you must also use the
2010-04-28 15:06:11 +02:00
\fB \- \- skip\- lock\- tables\fR
2015-09-09 14:32:52 +02:00
option\& .
2009-05-25 11:59:47 +02:00
.PP
2010-04-28 15:06:11 +02:00
To see a list of the options your version of
2024-09-03 19:15:59 +02:00
\fB mariadb-dump\fR
2009-05-25 11:59:47 +02:00
supports, execute
2024-09-03 19:15:59 +02:00
\fB mariadb-dump \- \- help\fR \& .
2009-05-25 11:59:47 +02:00
.PP
Some
2024-09-03 19:15:59 +02:00
\fB mariadb-dump\fR
2010-04-28 15:06:11 +02:00
options are shorthand for groups of other options:
.sp
.RS 4
.ie n \{ \
\h '-04'\(bu \h '+03'\c
. \}
.el \{ \
.sp -1
.IP \(bu 2 .3
. \}
Use of
2009-05-25 11:59:47 +02:00
\fB \- \- opt\fR
is the same as specifying
2010-04-28 15:06:11 +02:00
\fB \- \- add\- drop\- table\fR ,
\fB \- \- add\- locks\fR ,
\fB \- \- create\- options\fR ,
\fB \- \- disable\- keys\fR ,
\fB \- \- extended\- insert\fR ,
\fB \- \- lock\- tables\fR ,
\fB \- \- quick\fR , and
\fB \- \- set\- charset\fR \& . All of the options that
2009-05-25 11:59:47 +02:00
\fB \- \- opt\fR
stands for also are on by default because
\fB \- \- opt\fR
2009-09-16 14:03:18 +02:00
is on by default\& .
2010-04-28 15:06:11 +02:00
.RE
.sp
.RS 4
.ie n \{ \
\h '-04'\(bu \h '+03'\c
. \}
.el \{ \
.sp -1
.IP \(bu 2 .3
. \}
Use of
\fB \- \- compact\fR
is the same as specifying
\fB \- \- skip\- add\- drop\- table\fR ,
\fB \- \- skip\- add\- locks\fR ,
\fB \- \- skip\- comments\fR ,
\fB \- \- skip\- disable\- keys\fR , and
\fB \- \- skip\- set\- charset\fR
options\& .
.RE
2009-05-25 11:59:47 +02:00
.PP
To reverse the effect of a group option, uses its
\fB \- \- skip\- \fR \fB \fI xxx\fR \fR
form (\fB \- \- skip\- opt\fR
or
2009-09-16 14:03:18 +02:00
\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:
.sp
.RS 4
.ie n \{ \
\h '-04'\(bu \h '+03'\c
. \}
.el \{ \
.sp -1
.IP \(bu 2 .3
. \}
2009-05-25 11:59:47 +02:00
To select the effect of
\fB \- \- opt\fR
except for some features, use the
\fB \- \- skip\fR
2010-04-28 15:06:11 +02:00
option for each feature\& . To disable extended inserts and memory buffering, use
2009-05-25 11:59:47 +02:00
\fB \- \- opt\fR
\fB \- \- skip\- extended\- insert\fR
2010-04-28 15:06:11 +02:00
\fB \- \- skip\- quick\fR \& . (Actually,
2009-05-25 11:59:47 +02:00
\fB \- \- skip\- extended\- insert\fR
\fB \- \- skip\- quick\fR
is sufficient because
\fB \- \- opt\fR
2009-09-16 14:03:18 +02:00
is on by default\& .)
.RE
.sp
.RS 4
.ie n \{ \
\h '-04'\(bu \h '+03'\c
. \}
.el \{ \
.sp -1
.IP \(bu 2 .3
. \}
2009-05-25 11:59:47 +02:00
To reverse
\fB \- \- opt\fR
for all features except index disabling and table locking, use
\fB \- \- skip\- opt\fR
\fB \- \- disable\- keys\fR
2009-09-16 14:03:18 +02:00
\fB \- \- lock\- tables\fR \& .
2009-05-25 11:59:47 +02:00
.RE
.PP
2009-09-16 14:03:18 +02:00
When you selectively enable or disable the effect of a group option, order is important because options are processed first to last\& . For example,
2009-05-25 11:59:47 +02:00
\fB \- \- disable\- keys\fR
\fB \- \- lock\- tables\fR
\fB \- \- skip\- opt\fR
would not have the intended effect; it is the same as
\fB \- \- skip\- opt\fR
2009-09-16 14:03:18 +02:00
by itself\& .
2009-05-25 11:59:47 +02:00
.PP
2024-09-03 19:15:59 +02:00
\fB mariadb-dump\fR
2009-09-16 14:03:18 +02:00
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
2009-05-25 11:59:47 +02:00
\fB \- \- quick\fR
option (or
\fB \- \- opt\fR , which enables
2009-09-16 14:03:18 +02:00
\fB \- \- quick\fR )\& . The
2009-05-25 11:59:47 +02:00
\fB \- \- opt\fR
option (and hence
2010-04-28 15:06:11 +02:00
\fB \- \- quick\fR ) is enabled by default, so to enable memory buffering, use
2009-09-16 14:03:18 +02:00
\fB \- \- skip\- quick\fR \& .
2009-05-25 11:59:47 +02:00
.PP
If you are using a recent version of
2024-09-03 19:15:59 +02:00
\fB mariadb-dump\fR
2009-05-25 11:59:47 +02:00
to generate a dump to be reloaded into a very old MySQL server, you should not use the
\fB \- \- opt\fR
or
\fB \- \- extended\- insert\fR
2009-09-16 14:03:18 +02:00
option\& . Use
2009-05-25 11:59:47 +02:00
\fB \- \- skip\- opt\fR
2009-09-16 14:03:18 +02:00
instead\& .
.RE
2009-05-25 11:59:47 +02:00
.PP
2024-09-03 19:15:59 +02:00
\fB mariadb-dump\fR
2010-04-28 15:06:11 +02:00
supports the following options, which can be specified on the command line or in the
2024-09-03 19:15:59 +02:00
[mariadb-dump]
2010-04-28 15:06:11 +02:00
and
[client]
option file groups\& .
2024-09-03 19:15:59 +02:00
\fB mariadb-dump\fR
2015-09-09 14:32:52 +02:00
also supports the options for processing option file\& .
2009-09-16 14:03:18 +02:00
.sp
.RS 4
.ie n \{ \
\h '-04'\(bu \h '+03'\c
. \}
.el \{ \
.sp -1
.IP \(bu 2 .3
. \}
2024-09-03 19:15:59 +02:00
. \" mariadb-dump: help option
. \" help option: mariadb-dump
2009-05-25 11:59:47 +02:00
\fB \- \- help\fR ,
\fB \- ?\fR
.sp
2009-09-16 14:03:18 +02:00
Display a help message and exit\& .
.RE
.sp
.RS 4
.ie n \{ \
\h '-04'\(bu \h '+03'\c
. \}
.el \{ \
.sp -1
.IP \(bu 2 .3
. \}
2024-09-03 19:15:59 +02:00
. \" mariadb-dump: add-drop-database option
. \" add-drop-database option: mariadb-dump
2009-05-25 11:59:47 +02:00
\fB \- \- add\- drop\- database\fR
.sp
Add a
DROP DATABASE
statement before each
CREATE DATABASE
2010-04-28 15:06:11 +02:00
statement\& . This option is typically used in conjunction with the
\fB \- \- all\- databases\fR
or
\fB \- \- databases\fR
option because no
CREATE DATABASE
statements are written unless one of those options is specified\& .
2009-09-16 14:03:18 +02:00
.RE
.sp
.RS 4
.ie n \{ \
\h '-04'\(bu \h '+03'\c
. \}
.el \{ \
.sp -1
.IP \(bu 2 .3
. \}
2024-09-03 19:15:59 +02:00
. \" mariadb-dump: add-drop-table option
. \" add-drop-table option: mariadb-dump
2009-05-25 11:59:47 +02:00
\fB \- \- add\- drop\- table\fR
.sp
Add a
DROP TABLE
statement before each
CREATE TABLE
2009-09-16 14:03:18 +02:00
statement\& .
.RE
.sp
.RS 4
.ie n \{ \
\h '-04'\(bu \h '+03'\c
. \}
.el \{ \
.sp -1
.IP \(bu 2 .3
. \}
2024-09-03 19:15:59 +02:00
. \" mariadb-dump: add-drop-trigger option
. \" add-drop-trigger option: mariadb-dump
2017-05-05 13:32:42 +02:00
\fB \- \- add\- drop\- trigger\fR
.sp
Add a
DROP TRIGGER
statement before each
CREATE TRIGGER
statement\& .
.RE
.sp
.RS 4
.ie n \{ \
\h '-04'\(bu \h '+03'\c
. \}
.el \{ \
.sp -1
.IP \(bu 2 .3
. \}
2024-09-03 19:15:59 +02:00
. \" mariadb-dump: add-locks option
. \" add-locks option: mariadb-dump
2009-05-25 11:59:47 +02:00
\fB \- \- add\- locks\fR
.sp
Surround each table dump with
LOCK TABLES
and
UNLOCK TABLES
2015-09-09 14:32:52 +02:00
statements\& . This results in faster inserts when the dump file is reloaded\& .
2009-09-16 14:03:18 +02:00
.RE
.sp
.RS 4
.ie n \{ \
\h '-04'\(bu \h '+03'\c
. \}
.el \{ \
.sp -1
.IP \(bu 2 .3
. \}
2024-09-03 19:15:59 +02:00
. \" mariadb-dump: all-databases option
. \" all-databases option: mariadb-dump
2009-05-25 11:59:47 +02:00
\fB \- \- all\- databases\fR ,
\fB \- A\fR
.sp
2009-09-16 14:03:18 +02:00
Dump all tables in all databases\& . This is the same as using the
2009-05-25 11:59:47 +02:00
\fB \- \- databases\fR
2009-09-16 14:03:18 +02:00
option and naming all the databases on the command line\& .
.RE
.sp
.RS 4
.ie n \{ \
\h '-04'\(bu \h '+03'\c
. \}
.el \{ \
.sp -1
.IP \(bu 2 .3
. \}
2024-09-03 19:15:59 +02:00
. \" mariadb-dump: all-tablespaces option
. \" all-tablespaces option: mariadb-dump
2009-05-25 11:59:47 +02:00
\fB \- \- all\- tablespaces\fR ,
\fB \- Y\fR
.sp
Adds to a table dump all SQL statements needed to create any tablespaces used by an
NDBCLUSTER
2009-09-16 14:03:18 +02:00
table\& . This information is not otherwise included in the output from
2024-09-03 19:15:59 +02:00
\fB mariadb-dump\fR \& . This option is currently relevant only to MySQL Cluster tables\& .
2009-09-16 14:03:18 +02:00
.sp
.RE
2009-05-25 11:59:47 +02:00
.sp
2009-09-16 14:03:18 +02:00
.RS 4
.ie n \{ \
\h '-04'\(bu \h '+03'\c
. \}
.el \{ \
.sp -1
.IP \(bu 2 .3
. \}
2024-09-03 19:15:59 +02:00
. \" mariadb-dump: allow-keywords option
. \" allow-keywords option: mariadb-dump
2009-05-25 11:59:47 +02:00
\fB \- \- allow\- keywords\fR
.sp
2009-09-16 14:03:18 +02:00
Allow creation of column names that are keywords\& . This works by prefixing each column name with the table name\& .
.RE
.sp
.RS 4
.ie n \{ \
\h '-04'\(bu \h '+03'\c
. \}
.el \{ \
.sp -1
.IP \(bu 2 .3
. \}
2024-09-03 19:15:59 +02:00
. \" mariadb-dump: apply-slave-statements option
. \" apply-slave-statements option: mariadb-dump
2015-09-09 14:32:52 +02:00
\fB \- \- apply\- slave\- statements\fR
.sp
Adds 'STOP SLAVE' prior to 'CHANGE MASTER' and 'START SLAVE' to bottom of dump\& .
.RE
.sp
.RS 4
.ie n \{ \
\h '-04'\(bu \h '+03'\c
. \}
.el \{ \
.sp -1
.IP \(bu 2 .3
. \}
2024-09-03 19:15:59 +02:00
. \" mariadb-dump: as-of option
. \" as-of option: mariadb-dump
2024-07-16 14:41:56 +02:00
\fB \- \- as\- of=\fR \fB \fI name\fR \fR
.sp
Dump system versioned table as of specified timestamp\& .
.RE
.sp
.RS 4
.ie n \{ \
\h '-04'\(bu \h '+03'\c
. \}
.el \{ \
.sp -1
.IP \(bu 2 .3
. \}
2024-09-03 19:15:59 +02:00
. \" mariadb-dump: character-sets-dir option
. \" character-sets-dir option: mariadb-dump
2009-05-25 11:59:47 +02:00
\fB \- \- character\- sets\- dir=\fR \fB \fI path\fR \fR
.sp
2015-09-09 14:32:52 +02:00
The directory where character sets are installed\& .
2009-09-16 14:03:18 +02:00
.RE
.sp
.RS 4
.ie n \{ \
\h '-04'\(bu \h '+03'\c
. \}
.el \{ \
.sp -1
.IP \(bu 2 .3
. \}
2024-09-03 19:15:59 +02:00
. \" mariadb-dump: comments option
. \" comments option: mariadb-dump
2009-05-25 11:59:47 +02:00
\fB \- \- comments\fR ,
\fB \- i\fR
.sp
2009-09-16 14:03:18 +02:00
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
\fB \- \- skip\- comments\fR \& .
.RE
.sp
.RS 4
.ie n \{ \
\h '-04'\(bu \h '+03'\c
. \}
.el \{ \
.sp -1
.IP \(bu 2 .3
. \}
2024-09-03 19:15:59 +02:00
. \" mariadb-dump: compact option
. \" compact option: mariadb-dump
2009-05-25 11:59:47 +02:00
\fB \- \- compact\fR
.sp
2010-04-28 15:06:11 +02:00
Produce more compact output\& . This option enables the
2009-05-25 11:59:47 +02:00
\fB \- \- skip\- add\- drop\- table\fR ,
\fB \- \- skip\- add\- locks\fR ,
\fB \- \- skip\- comments\fR ,
\fB \- \- skip\- disable\- keys\fR , and
\fB \- \- skip\- set\- charset\fR
2009-09-16 14:03:18 +02:00
options\& .
.RE
.RE
.sp
.RS 4
.ie n \{ \
\h '-04'\(bu \h '+03'\c
. \}
.el \{ \
.sp -1
.IP \(bu 2 .3
. \}
2024-09-03 19:15:59 +02:00
. \" mariadb-dump: compatible option
. \" compatible option: mariadb-dump
2009-05-25 11:59:47 +02:00
\fB \- \- compatible=\fR \fB \fI name\fR \fR
.sp
2009-09-16 14:03:18 +02:00
Produce output that is more compatible with other database systems or with older MySQL servers\& . The value of
2010-04-28 15:06:11 +02:00
\fI name\fR
2009-05-25 11:59:47 +02:00
can be
ansi,
mysql323,
mysql40,
postgresql,
oracle,
mssql,
db2,
maxdb,
no_key_options,
no_table_options, or
2015-09-09 14:32:52 +02:00
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\& .
2009-05-25 11:59:47 +02:00
.sp
2009-09-16 14:03:18 +02:00
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,
2009-05-25 11:59:47 +02:00
\fB \- \- compatible=oracle\fR
2009-09-16 14:03:18 +02:00
does not map data types to Oracle types or use Oracle comment syntax\& .
2009-05-25 11:59:47 +02:00
.sp
2009-09-16 14:03:18 +02:00
.RE
.sp
.RS 4
.ie n \{ \
\h '-04'\(bu \h '+03'\c
. \}
.el \{ \
.sp -1
.IP \(bu 2 .3
. \}
2024-09-03 19:15:59 +02:00
. \" mariadb-dump: complete-insert option
. \" complete-insert option: mariadb-dump
2009-05-25 11:59:47 +02:00
\fB \- \- complete\- insert\fR ,
\fB \- c\fR
.sp
Use complete
INSERT
2009-09-16 14:03:18 +02:00
statements that include column names\& .
.RE
.sp
.RS 4
.ie n \{ \
\h '-04'\(bu \h '+03'\c
. \}
.el \{ \
.sp -1
.IP \(bu 2 .3
. \}
2024-09-03 19:15:59 +02:00
. \" mariadb-dump: compress option
. \" compress option: mariadb-dump
2009-05-25 11:59:47 +02:00
\fB \- \- compress\fR ,
\fB \- C\fR
.sp
2009-09-16 14:03:18 +02:00
Compress all information sent between the client and the server if both support compression\& .
.RE
.sp
.RS 4
.ie n \{ \
\h '-04'\(bu \h '+03'\c
. \}
.el \{ \
.sp -1
.IP \(bu 2 .3
. \}
2024-09-03 19:15:59 +02:00
. \" mariadb-dump: copy-s3-tables option
. \" copy-s3-tables option: mariadb-dump
2019-09-10 13:58:58 +02:00
\fB \- \- copy\- s3\- tables\fR
.sp
MDEV-23789: Fix unnecessary acute accents in man pages
The man pages has several places where \' is intended to escape the single
quote and just print '. However, in reality this will print an ` (acute
accent). Fix this by removing excess backslashes. Also remove some excess
& in front of dots, such escaping is also unnecessary.
Also join several lines to avoid lone words in quotes to be read by groff
as macros when they are just text.
In a table (t{}) the content must be on new lines separately, so groff
will try to read them as macros too, so use \(aq that renders to '
(single quote).
This error was originally detected by Lintian:
https://lintian.debian.org/tags/acute-accent-in-manual-page
Example of man page sections before and after:
Make a backup of each table´s data file using the name tbl_name.OLD.
->
Make a backup of each table's data file using the name tbl_name.OLD.
A typical debug_options string is ´d:t:o,file_name´.
The default is ´d:t:o,/tmp/my_print_defaults.trace´.
->
A typical debug_options string is 'd:t:o,file_name'.
The default is 'd:t:o,/tmp/my_print_defaults.trace'.
shell> mysql --xml -uroot -e "SHOW VARIABLES LIKE ´version%´"
<?xml version="1.0"?>
<resultset statement="SHOW VARIABLES LIKE ´version%´" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
->
shell> mysql --xml -uroot -e "SHOW VARIABLES LIKE 'version%'"
<?xml version="1.0"?>
<resultset statement="SHOW VARIABLES LIKE 'version%'" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
This command was used to validate no man pages have syntax errors:
for x in *.?
do
echo "##### $x #####"
LC_ALL=C.UTF-8 MANROFFSEQ='' MANWIDTH=80 man --warnings -E UTF-8 -l -Tutf8 -Z $x >/dev/null
done
The man pages are not perfect after this, there are still a lot of
suboptimal syntax, but this helps towards better man pages.
All new code of the whole pull request, including one or several files
that are either new files or modified ones, are contributed under the
BSD-new license. I am contributing on behalf of my employer Amazon Web
Services, Inc.
2023-03-11 13:01:39 -08:00
By default S3 tables are ignored\& . With this option set, the result file will contain a CREATE statement
2019-09-10 13:58:58 +02:00
for a similar Aria table, followed by the table data and ending with an ALTER TABLE xxx ENGINE=S3\& .
.RE
.sp
.RS 4
.ie n \{ \
\h '-04'\(bu \h '+03'\c
. \}
.el \{ \
.sp -1
.IP \(bu 2 .3
. \}
2024-09-03 19:15:59 +02:00
. \" mariadb-dump: create-options option
. \" create-options option: mariadb-dump
2013-06-13 00:13:23 +02:00
\fB \- \- create\- options\fR ,
\fB \- a\fR
2009-05-25 11:59:47 +02:00
.sp
2015-09-09 14:32:52 +02:00
Include all MariaDB\- specific table options in the
2009-05-25 11:59:47 +02:00
CREATE TABLE
2015-09-09 14:32:52 +02:00
statements\& . Use \fB \- \- skip-create-options\fR to disable.
2009-09-16 14:03:18 +02:00
.RE
.sp
.RS 4
.ie n \{ \
\h '-04'\(bu \h '+03'\c
. \}
.el \{ \
.sp -1
.IP \(bu 2 .3
. \}
2024-09-03 19:15:59 +02:00
. \" mariadb-dump: databases option
. \" databases option: mariadb-dump
2009-05-25 11:59:47 +02:00
\fB \- \- databases\fR ,
\fB \- B\fR
.sp
2009-09-16 14:03:18 +02:00
Dump several databases\& . Normally,
2024-09-03 19:15:59 +02:00
\fB mariadb-dump\fR
2009-09-16 14:03:18 +02:00
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\& .
2009-05-25 11:59:47 +02:00
CREATE DATABASE
and
USE
2009-09-16 14:03:18 +02:00
statements are included in the output before each new database\& .
.RE
.sp
.RS 4
.ie n \{ \
\h '-04'\(bu \h '+03'\c
. \}
.el \{ \
.sp -1
.IP \(bu 2 .3
. \}
2024-09-03 19:15:59 +02:00
. \" mariadb-dump: debug option
. \" debug option: mariadb-dump
2009-05-25 11:59:47 +02:00
\fB \- \- debug[=\fR \fB \fI debug_options\fR \fR \fB ]\fR ,
\fB \- # [\fR \fB \fI debug_options\fR \fR \fB ]\fR
.sp
2009-09-16 14:03:18 +02:00
Write a debugging log\& . A typical
2009-05-25 11:59:47 +02:00
\fI debug_options\fR
2024-09-03 19:15:59 +02:00
string is 'd:t:o,\fI file_name\fR '. The default value is 'd:t:o,/tmp/mariadb-dump.trace'.
2009-09-16 14:03:18 +02:00
.RE
.sp
.RS 4
.ie n \{ \
\h '-04'\(bu \h '+03'\c
. \}
.el \{ \
.sp -1
.IP \(bu 2 .3
. \}
2024-09-03 19:15:59 +02:00
. \" mariadb-dump: debug-check option
. \" debug-check option: mariadb-dump
2009-05-25 11:59:47 +02:00
\fB \- \- debug\- check\fR
.sp
2015-09-09 14:32:52 +02:00
Print some debugging information when the program exits\& .
2009-09-16 14:03:18 +02:00
.RE
.sp
.RS 4
.ie n \{ \
\h '-04'\(bu \h '+03'\c
. \}
.el \{ \
.sp -1
.IP \(bu 2 .3
. \}
2024-09-03 19:15:59 +02:00
. \" mariadb-dump: debug-info option
. \" debug-info option: mariadb-dump
2009-05-25 11:59:47 +02:00
\fB \- \- debug\- info\fR
.sp
2015-09-09 14:32:52 +02:00
Print debugging information and memory and CPU usage statistics when the program exits\& .
.RE
.sp
.RS 4
.ie n \{ \
\h '-04'\(bu \h '+03'\c
. \}
.el \{ \
.sp -1
.IP \(bu 2 .3
. \}
2024-09-03 19:15:59 +02:00
. \" mariadb-dump: default-auth option
. \" default-auth option: mariadb-dump
2015-09-09 14:32:52 +02:00
\fB \- \- default\- auth\fR
.sp
Default authentication client-side plugin to use\& .
2009-09-16 14:03:18 +02:00
.RE
.sp
.RS 4
.ie n \{ \
\h '-04'\(bu \h '+03'\c
. \}
.el \{ \
.sp -1
.IP \(bu 2 .3
. \}
2024-09-03 19:15:59 +02:00
. \" mariadb-dump: default-character-set option
. \" default-character-set option: mariadb-dump
2009-05-25 11:59:47 +02:00
\fB \- \- default\- character\- set=\fR \fB \fI charset_name\fR \fR
.sp
Use
\fI charset_name\fR
2015-09-09 14:32:52 +02:00
as the default character set\& . If no character set is specified,
2024-09-03 19:15:59 +02:00
\fB mariadb-dump\fR
2009-05-25 11:59:47 +02:00
uses
2015-09-09 14:32:52 +02:00
utf8\& .
2009-05-25 11:59:47 +02:00
.sp
2009-09-16 14:03:18 +02:00
.RE
.sp
.RS 4
.ie n \{ \
\h '-04'\(bu \h '+03'\c
. \}
.el \{ \
.sp -1
.IP \(bu 2 .3
. \}
2024-09-03 19:15:59 +02:00
. \" mariadb-dump: defaults-extra-file option
. \" defaults-extra-file option: mariadb-dump
2013-06-13 00:13:23 +02:00
\fB \- \- defaults\- extra\- file=\fR \fB \fI filename\fR \fR
.sp
Set \fB \fI filename\fR \fR as the file to read default options from after the global defaults files has been read\& .
Must be given as first option\& .
.RE
.sp
.RS 4
.ie n \{ \
\h '-04'\(bu \h '+03'\c
. \}
.el \{ \
.sp -1
.IP \(bu 2 .3
. \}
2024-09-03 19:15:59 +02:00
. \" mariadb-dump: defaults-file option
. \" defaults-file option: mariadb-dump
2013-06-13 00:13:23 +02:00
\fB \- \- defaults\- file=\fR \fB \fI filename\fR \fR
.sp
Set \fB \fI filename\fR \fR as the file to read default options from, override global defaults files\& .
Must be given as first option\& .
.RE
.sp
.RS 4
.ie n \{ \
\h '-04'\(bu \h '+03'\c
. \}
.el \{ \
.sp -1
.IP \(bu 2 .3
. \}
2015-09-09 14:32:52 +02:00
. \" my_print_defaults: defaults-group-suffix option
. \" defaults-group-suffix option: my_print_defaults
\fB \- \- defaults\- group\- suffix=\fR \fB \fI str\fR \fR ,
.sp
2024-09-03 19:15:59 +02:00
Also read groups with a suffix of \fI str\fR \& . For example, since mariadb-dump normally reads the [client] and [mariadb-dump] groups, \- \- defaults\- group\- suffix=x would cause it to also read the groups [mariadb-dump_x] and [client_x]\& .
2015-09-09 14:32:52 +02:00
.RE
.sp
.RS 4
.ie n \{ \
\h '-04'\(bu \h '+03'\c
. \}
.el \{ \
.sp -1
.IP \(bu 2 .3
. \}
2024-09-03 19:15:59 +02:00
. \" mariadb-dump: delayed-insert option
. \" delayed-insert option: mariadb-dump
2009-05-25 11:59:47 +02:00
\fB \- \- delayed\- insert\fR
.sp
Write
INSERT DELAYED
statements rather than
INSERT
2009-09-16 14:03:18 +02:00
statements\& .
.RE
.sp
.RS 4
.ie n \{ \
\h '-04'\(bu \h '+03'\c
. \}
.el \{ \
.sp -1
.IP \(bu 2 .3
. \}
2024-09-03 19:15:59 +02:00
. \" mariadb-dump: delete-master-logs option
. \" delete-master-logs option: mariadb-dump
2009-05-25 11:59:47 +02:00
\fB \- \- delete\- master\- logs\fR
.sp
2010-04-28 15:06:11 +02:00
On a master replication server, delete the binary logs by sending a
PURGE BINARY LOGS
statement to the server after performing the dump operation\& . This option automatically enables
2009-09-16 14:03:18 +02:00
\fB \- \- master\- data\fR \& .
.RE
.sp
.RS 4
.ie n \{ \
\h '-04'\(bu \h '+03'\c
. \}
.el \{ \
.sp -1
.IP \(bu 2 .3
. \}
2024-10-08 14:05:12 +02:00
. \" mariadb-dump: dir option
. \" dirs option: mariadb-dump
\fB \- \- dir\fR
.sp
Parallel dump of multiple databases. Works just like \fB \- \- tab\fR , with regard to output
(sql file for table definition and tab-separated for data, same options, e.g \fB \- \- parallel\fR )\& .
It also allows the \fB \- \- databases\fR and \fB \- \- all-databases\fR options\& . When \fB \- \- dir\fR is used,
it creates the directory structure in the output directory pointed to by \fB \- \- dir\fR \& . For
every database to be dumped, there will be a directory with the database name\& . All
options that \fB \- \- tab\fR supports are also supported by \fB \- \- dir\fR , in particular \fB \- \- parallel\fR \& .
.RE
.sp
.RS 4
.ie n \{ \
\h '-04'\(bu \h '+03'\c
. \}
.el \{ \
.sp -1
.IP \(bu 2 .3
. \}
2024-09-03 19:15:59 +02:00
. \" mariadb-dump: disable-keys option
. \" disable-keys option: mariadb-dump
2009-05-25 11:59:47 +02:00
\fB \- \- disable\- keys\fR ,
\fB \- K\fR
.sp
For each table, surround the
INSERT
statements with
/*!40000 ALTER TABLE \fI tbl_name\fR DISABLE KEYS */;
and
/*!40000 ALTER TABLE \fI tbl_name\fR ENABLE KEYS */;
2009-09-16 14:03:18 +02:00
statements\& . This makes loading the dump file faster because the indexes are created after all rows are inserted\& . This option is effective only for nonunique indexes of
2009-05-25 11:59:47 +02:00
MyISAM
2009-09-16 14:03:18 +02:00
tables\& .
.RE
.sp
.RS 4
.ie n \{ \
\h '-04'\(bu \h '+03'\c
. \}
.el \{ \
.sp -1
.IP \(bu 2 .3
. \}
2024-09-03 19:15:59 +02:00
. \" mariadb-dump: dump-date option
. \" dump-date option: mariadb-dump
2009-05-25 11:59:47 +02:00
\fB \- \- dump\- date\fR
.sp
2010-04-28 15:06:11 +02:00
If the
\fB \- \- comments\fR
option is given,
2024-09-03 19:15:59 +02:00
\fB mariadb-dump\fR
2010-04-28 15:06:11 +02:00
produces a comment at the end of the dump of the following form:
.sp
.if n \{ \
.RS 4
. \}
.nf
2009-05-25 11:59:47 +02:00
\- \- Dump completed on \fI DATE\fR
2010-04-28 15:06:11 +02:00
.fi
.if n \{ \
.RE
. \}
.sp
However, the date causes dump files taken at different times to appear to be different, even if the data are otherwise identical\& .
2009-05-25 11:59:47 +02:00
\fB \- \- dump\- date\fR
and
\fB \- \- skip\- dump\- date\fR
2009-09-16 14:03:18 +02:00
control whether the date is added to the comment\& . The default is
2009-05-25 11:59:47 +02:00
\fB \- \- dump\- date\fR
2009-09-16 14:03:18 +02:00
(include the date in the comment)\& .
2009-05-25 11:59:47 +02:00
\fB \- \- skip\- dump\- date\fR
2015-09-09 14:32:52 +02:00
suppresses date printing\&
2009-09-16 14:03:18 +02:00
.RE
.sp
.RS 4
.ie n \{ \
\h '-04'\(bu \h '+03'\c
. \}
.el \{ \
.sp -1
.IP \(bu 2 .3
. \}
2024-09-03 19:15:59 +02:00
. \" mariadb-dump: dump-history option
. \" dump-history option: mariadb-dump
2024-07-16 14:41:56 +02:00
\fB \- \- dump\- history\fR
.sp
Dump tables with history. Until this option, mariadb-dump could not read historical rows from versioned tables,
and so historical data would not be backed up\& .
.RE
.sp
.RS 4
.ie n \{ \
\h '-04'\(bu \h '+03'\c
. \}
.el \{ \
.sp -1
.IP \(bu 2 .3
. \}
2024-09-03 19:15:59 +02:00
. \" mariadb-dump: dump-slave option
. \" dump-slave option: mariadb-dump
2016-12-06 13:18:48 +02:00
\fB \- \- dump\- slave[=\fR \fB \fI value\fR \fR \fB ]\fR
.sp
MDEV-23789: Fix unnecessary acute accents in man pages
The man pages has several places where \' is intended to escape the single
quote and just print '. However, in reality this will print an ` (acute
accent). Fix this by removing excess backslashes. Also remove some excess
& in front of dots, such escaping is also unnecessary.
Also join several lines to avoid lone words in quotes to be read by groff
as macros when they are just text.
In a table (t{}) the content must be on new lines separately, so groff
will try to read them as macros too, so use \(aq that renders to '
(single quote).
This error was originally detected by Lintian:
https://lintian.debian.org/tags/acute-accent-in-manual-page
Example of man page sections before and after:
Make a backup of each table´s data file using the name tbl_name.OLD.
->
Make a backup of each table's data file using the name tbl_name.OLD.
A typical debug_options string is ´d:t:o,file_name´.
The default is ´d:t:o,/tmp/my_print_defaults.trace´.
->
A typical debug_options string is 'd:t:o,file_name'.
The default is 'd:t:o,/tmp/my_print_defaults.trace'.
shell> mysql --xml -uroot -e "SHOW VARIABLES LIKE ´version%´"
<?xml version="1.0"?>
<resultset statement="SHOW VARIABLES LIKE ´version%´" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
->
shell> mysql --xml -uroot -e "SHOW VARIABLES LIKE 'version%'"
<?xml version="1.0"?>
<resultset statement="SHOW VARIABLES LIKE 'version%'" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
This command was used to validate no man pages have syntax errors:
for x in *.?
do
echo "##### $x #####"
LC_ALL=C.UTF-8 MANROFFSEQ='' MANWIDTH=80 man --warnings -E UTF-8 -l -Tutf8 -Z $x >/dev/null
done
The man pages are not perfect after this, there are still a lot of
suboptimal syntax, but this helps towards better man pages.
All new code of the whole pull request, including one or several files
that are either new files or modified ones, are contributed under the
BSD-new license. I am contributing on behalf of my employer Amazon Web
Services, Inc.
2023-03-11 13:01:39 -08:00
Used for producing a dump file from a replication slave server that can be used to set up another slave server
with the same master\& . Causes the binary log position and filename of the master to be appended to the dumped
data output\& . Setting the value to 1 (the default) will print it as a CHANGE MASTER command in the dumped data
output; if set to 2, that command will be prefixed with a comment symbol\& . This option will turn
\- \- lock\- all\- tables on, unless \- \- single-transaction is specified too (in which case a global read lock is only
taken a short time at the beginning of the dump \- don't forget to read about \- \- single-transaction below)\& . In
all cases any action on logs will happen at the exact moment of the dump\& . Option automatically turns
2024-09-03 19:15:59 +02:00
\- \- lock\- tables off\& . Using this option causes mariadb-dump to stop the slave SQL thread before beginning the dump,
2016-12-06 13:18:48 +02:00
and restart it again after completion\& .
.RE
.sp
.RS 4
.ie n \{ \
\h '-04'\(bu \h '+03'\c
. \}
.el \{ \
.sp -1
.IP \(bu 2 .3
. \}
2024-09-03 19:15:59 +02:00
. \" mariadb-dump: events option
. \" events option: mariadb-dump
2009-05-25 11:59:47 +02:00
\fB \- \- events\fR ,
\fB \- E\fR
.sp
2015-09-09 14:32:52 +02:00
Include Event Scheduler events for the dumped databases in the output\& .
2009-09-16 14:03:18 +02:00
.RE
.sp
.RS 4
.ie n \{ \
\h '-04'\(bu \h '+03'\c
. \}
.el \{ \
.sp -1
.IP \(bu 2 .3
. \}
2024-09-03 19:15:59 +02:00
. \" mariadb-dump: extended-insert option
. \" extended-insert option: mariadb-dump
2009-05-25 11:59:47 +02:00
\fB \- \- extended\- insert\fR ,
\fB \- e\fR
.sp
Use multiple\- row
INSERT
syntax that include several
VALUES
2009-09-16 14:03:18 +02:00
lists\& . This results in a smaller dump file and speeds up inserts when the file is reloaded\& .
.RE
.sp
.RS 4
.ie n \{ \
\h '-04'\(bu \h '+03'\c
. \}
.el \{ \
.sp -1
.IP \(bu 2 .3
. \}
2024-09-03 19:15:59 +02:00
. \" mariadb-dump: fields-terminated-by option
. \" fields-terminated-by option: mariadb-dump
2009-09-16 14:03:18 +02:00
\fB \- \- fields\- terminated\- by=\& .\& .\& .\fR ,
2024-09-03 19:15:59 +02:00
. \" mariadb-dump: fields-enclosed-by option
. \" fields-enclosed-by option: mariadb-dump
2009-09-16 14:03:18 +02:00
\fB \- \- fields\- enclosed\- by=\& .\& .\& .\fR ,
2024-09-03 19:15:59 +02:00
. \" mariadb-dump: fields-optionally-enclosed-by option
. \" fields-optionally-enclosed-by option: mariadb-dump
2009-09-16 14:03:18 +02:00
\fB \- \- fields\- optionally\- enclosed\- by=\& .\& .\& .\fR ,
2024-09-03 19:15:59 +02:00
. \" mariadb-dump: fields-escaped-by option
. \" fields-escaped-by option: mariadb-dump
2009-09-16 14:03:18 +02:00
\fB \- \- fields\- escaped\- by=\& .\& .\& .\fR
2009-05-25 11:59:47 +02:00
.sp
These options are used with the
2010-04-28 15:06:11 +02:00
\fB \- \- tab\fR
option and have the same meaning as the corresponding
FIELDS
clauses for
2015-09-09 14:32:52 +02:00
LOAD DATA INFILE\& .
2009-09-16 14:03:18 +02:00
.RE
.sp
.RS 4
.ie n \{ \
\h '-04'\(bu \h '+03'\c
. \}
.el \{ \
.sp -1
.IP \(bu 2 .3
. \}
2024-09-03 19:15:59 +02:00
. \" mariadb-dump: first-slave option
. \" first-slave option: mariadb-dump
2010-04-28 15:06:11 +02:00
\fB \- \- first\- slave\fR
2009-05-25 11:59:47 +02:00
.sp
2015-09-09 14:32:52 +02:00
Removed in MariaDB 5.5\& . Use
2010-04-28 15:06:11 +02:00
\fB \- \- lock\- all\- tables\fR
instead\& .
2009-09-16 14:03:18 +02:00
.RE
.sp
.RS 4
.ie n \{ \
\h '-04'\(bu \h '+03'\c
. \}
.el \{ \
.sp -1
.IP \(bu 2 .3
. \}
2024-09-03 19:15:59 +02:00
. \" mariadb-dump: flush-logs option
. \" flush-logs option: mariadb-dump
2009-05-25 11:59:47 +02:00
\fB \- \- flush\- logs\fR ,
\fB \- F\fR
.sp
2015-09-09 14:32:52 +02:00
Flush the MariaDB server log files before starting the dump\& . This option requires the
2009-05-25 11:59:47 +02:00
RELOAD
2010-04-28 15:06:11 +02:00
privilege\& . If you use this option in combination with the
2009-05-25 11:59:47 +02:00
\fB \- \- all\- databases\fR
2010-04-28 15:06:11 +02:00
option, the logs are flushed
2009-09-16 14:03:18 +02:00
\fI for each database dumped\fR \& . The exception is when using
2009-05-25 11:59:47 +02:00
\fB \- \- lock\- all\- tables\fR
or
2009-09-16 14:03:18 +02:00
\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
2009-05-25 11:59:47 +02:00
\fB \- \- flush\- logs\fR
together with either
\fB \- \- lock\- all\- tables\fR
or
2009-09-16 14:03:18 +02:00
\fB \- \- master\- data\fR \& .
.RE
.sp
.RS 4
.ie n \{ \
\h '-04'\(bu \h '+03'\c
. \}
.el \{ \
.sp -1
.IP \(bu 2 .3
. \}
2024-09-03 19:15:59 +02:00
. \" mariadb-dump: flush-privileges option
. \" flush-privileges option: mariadb-dump
2009-05-25 11:59:47 +02:00
\fB \- \- flush\- privileges\fR
.sp
2010-04-28 15:06:11 +02:00
Send a
2009-05-25 11:59:47 +02:00
FLUSH PRIVILEGES
2010-04-28 15:06:11 +02:00
statement to the server after dumping the
2009-05-25 11:59:47 +02:00
mysql
2009-09-16 14:03:18 +02:00
database\& . This option should be used any time the dump contains the
2009-05-25 11:59:47 +02:00
mysql
database and any other database that depends on the data in the
mysql
2015-09-09 14:32:52 +02:00
database for proper restoration\& .
2009-09-16 14:03:18 +02:00
.RE
.sp
.RS 4
.ie n \{ \
\h '-04'\(bu \h '+03'\c
. \}
.el \{ \
.sp -1
.IP \(bu 2 .3
. \}
2024-09-03 19:15:59 +02:00
. \" mariadb-dump: force option
. \" force option: mariadb-dump
2009-05-25 11:59:47 +02:00
\fB \- \- force\fR ,
\fB \- f\fR
.sp
2009-09-16 14:03:18 +02:00
Continue even if an SQL error occurs during a table dump\& .
2009-05-25 11:59:47 +02:00
.sp
One use for this option is to cause
2024-09-03 19:15:59 +02:00
\fB mariadb-dump\fR
2009-09-16 14:03:18 +02:00
to continue executing even when it encounters a view that has become invalid because the definition refers to a table that has been dropped\& . Without
2009-05-25 11:59:47 +02:00
\fB \- \- force\fR ,
2024-09-03 19:15:59 +02:00
\fB mariadb-dump\fR
2009-09-16 14:03:18 +02:00
exits with an error message\& . With
2009-05-25 11:59:47 +02:00
\fB \- \- force\fR ,
2024-09-03 19:15:59 +02:00
\fB mariadb-dump\fR
2009-09-16 14:03:18 +02:00
prints the error message, but it also writes an SQL comment containing the view definition to the dump output and continues executing\& .
.RE
.sp
.RS 4
.ie n \{ \
\h '-04'\(bu \h '+03'\c
. \}
.el \{ \
.sp -1
.IP \(bu 2 .3
. \}
2024-09-03 19:15:59 +02:00
. \" mariadb-dump: gtid option
. \" gtid option: mariadb-dump
2015-09-09 14:32:52 +02:00
\fB \- \- gtid\fR
2009-05-25 11:59:47 +02:00
.sp
2015-09-09 14:32:52 +02:00
Available from MariaDB 10.0.13, and is used together with \fB \- \- master\- data\fR and \fB \- \- dump\- slave\fR to more conveniently set up a new GTID slave\& . It causes those options to output SQL statements that configure the slave to use the global transaction ID to connect to the master instead of old-style filename/offset positions\& . The old-style positions are still included in comments when \fB \- \- gtid\fR is used; likewise the GTID position is included in comments even if \fB \- \- gtid\fR is not used\& .
2009-09-16 14:03:18 +02:00
.RE
.sp
.RS 4
.ie n \{ \
\h '-04'\(bu \h '+03'\c
. \}
.el \{ \
.sp -1
.IP \(bu 2 .3
. \}
2024-09-03 19:15:59 +02:00
. \" mariadb-dump: header option
. \" header option: mariadb-dump
2022-10-20 18:42:48 +01:00
\fB \- \- header\fR
.sp
Used together with --tab. When enabled, adds header with column names to the top of output txt files.
.RE
.sp
.RS 4
.ie n \{ \
\h '-04'\(bu \h '+03'\c
. \}
.el \{ \
.sp -1
.IP \(bu 2 .3
. \}
2024-09-03 19:15:59 +02:00
. \" mariadb-dump: hex-blob option
. \" hex-blob option: mariadb-dump
2009-05-25 11:59:47 +02:00
\fB \- \- hex\- blob\fR
.sp
MDEV-23789: Fix unnecessary acute accents in man pages
The man pages has several places where \' is intended to escape the single
quote and just print '. However, in reality this will print an ` (acute
accent). Fix this by removing excess backslashes. Also remove some excess
& in front of dots, such escaping is also unnecessary.
Also join several lines to avoid lone words in quotes to be read by groff
as macros when they are just text.
In a table (t{}) the content must be on new lines separately, so groff
will try to read them as macros too, so use \(aq that renders to '
(single quote).
This error was originally detected by Lintian:
https://lintian.debian.org/tags/acute-accent-in-manual-page
Example of man page sections before and after:
Make a backup of each table´s data file using the name tbl_name.OLD.
->
Make a backup of each table's data file using the name tbl_name.OLD.
A typical debug_options string is ´d:t:o,file_name´.
The default is ´d:t:o,/tmp/my_print_defaults.trace´.
->
A typical debug_options string is 'd:t:o,file_name'.
The default is 'd:t:o,/tmp/my_print_defaults.trace'.
shell> mysql --xml -uroot -e "SHOW VARIABLES LIKE ´version%´"
<?xml version="1.0"?>
<resultset statement="SHOW VARIABLES LIKE ´version%´" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
->
shell> mysql --xml -uroot -e "SHOW VARIABLES LIKE 'version%'"
<?xml version="1.0"?>
<resultset statement="SHOW VARIABLES LIKE 'version%'" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
This command was used to validate no man pages have syntax errors:
for x in *.?
do
echo "##### $x #####"
LC_ALL=C.UTF-8 MANROFFSEQ='' MANWIDTH=80 man --warnings -E UTF-8 -l -Tutf8 -Z $x >/dev/null
done
The man pages are not perfect after this, there are still a lot of
suboptimal syntax, but this helps towards better man pages.
All new code of the whole pull request, including one or several files
that are either new files or modified ones, are contributed under the
BSD-new license. I am contributing on behalf of my employer Amazon Web
Services, Inc.
2023-03-11 13:01:39 -08:00
Dump binary columns using hexadecimal notation (for example, 'abc' becomes
2009-09-16 14:03:18 +02:00
0x616263)\& . The affected data types are
2009-05-25 11:59:47 +02:00
BINARY,
2010-04-28 15:06:11 +02:00
VARBINARY, the
BLOB
types, and
2009-09-16 14:03:18 +02:00
BIT\& .
.RE
.sp
.RS 4
.ie n \{ \
\h '-04'\(bu \h '+03'\c
. \}
.el \{ \
.sp -1
.IP \(bu 2 .3
. \}
2024-09-03 19:15:59 +02:00
. \" mariadb-dump: host option
. \" host option: mariadb-dump
2015-09-09 14:32:52 +02:00
\fB \- \- host=\fR \fB \fI host_name\fR \fR ,
\fB \- h \fR \fB \fI host_name\fR \fR
.sp
Dump data from the MariaDB server on the given host\& . The default host is
localhost\& .
.RE
.sp
.RS 4
.ie n \{ \
\h '-04'\(bu \h '+03'\c
. \}
.el \{ \
.sp -1
.IP \(bu 2 .3
. \}
2024-09-03 19:15:59 +02:00
. \" mariadb-dump: ignore-table option
. \" ignore-table option: mariadb-dump
2009-09-16 14:03:18 +02:00
\fB \- \- ignore\- table=\fR \fB \fI db_name\& .tbl_name\fR \fR
.sp
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\& . This option also can be used to ignore views\& .
.RE
.sp
.RS 4
.ie n \{ \
\h '-04'\(bu \h '+03'\c
. \}
.el \{ \
.sp -1
.IP \(bu 2 .3
. \}
2024-09-03 19:15:59 +02:00
. \" mariadb-dump: include-master-host-port option
. \" include-master-host-port option: mariadb-dump
2015-09-09 14:32:52 +02:00
\fB \- \- include\- master\- host\- port\fR
.sp
MDEV-23789: Fix unnecessary acute accents in man pages
The man pages has several places where \' is intended to escape the single
quote and just print '. However, in reality this will print an ` (acute
accent). Fix this by removing excess backslashes. Also remove some excess
& in front of dots, such escaping is also unnecessary.
Also join several lines to avoid lone words in quotes to be read by groff
as macros when they are just text.
In a table (t{}) the content must be on new lines separately, so groff
will try to read them as macros too, so use \(aq that renders to '
(single quote).
This error was originally detected by Lintian:
https://lintian.debian.org/tags/acute-accent-in-manual-page
Example of man page sections before and after:
Make a backup of each table´s data file using the name tbl_name.OLD.
->
Make a backup of each table's data file using the name tbl_name.OLD.
A typical debug_options string is ´d:t:o,file_name´.
The default is ´d:t:o,/tmp/my_print_defaults.trace´.
->
A typical debug_options string is 'd:t:o,file_name'.
The default is 'd:t:o,/tmp/my_print_defaults.trace'.
shell> mysql --xml -uroot -e "SHOW VARIABLES LIKE ´version%´"
<?xml version="1.0"?>
<resultset statement="SHOW VARIABLES LIKE ´version%´" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
->
shell> mysql --xml -uroot -e "SHOW VARIABLES LIKE 'version%'"
<?xml version="1.0"?>
<resultset statement="SHOW VARIABLES LIKE 'version%'" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
This command was used to validate no man pages have syntax errors:
for x in *.?
do
echo "##### $x #####"
LC_ALL=C.UTF-8 MANROFFSEQ='' MANWIDTH=80 man --warnings -E UTF-8 -l -Tutf8 -Z $x >/dev/null
done
The man pages are not perfect after this, there are still a lot of
suboptimal syntax, but this helps towards better man pages.
All new code of the whole pull request, including one or several files
that are either new files or modified ones, are contributed under the
BSD-new license. I am contributing on behalf of my employer Amazon Web
Services, Inc.
2023-03-11 13:01:39 -08:00
Add the MASTER_HOST and MASTER_PORT options for the CHANGE MASTER TO statement when using
2015-09-09 14:32:52 +02:00
the \fB --dump-slave\fR option for a slave dump\& .
.RE
.sp
.RS 4
.ie n \{ \
\h '-04'\(bu \h '+03'\c
. \}
.el \{ \
.sp -1
.IP \(bu 2 .3
. \}
2024-09-03 19:15:59 +02:00
. \" mariadb-dump: insert-ignore option
. \" insert-ignore option: mariadb-dump
2009-05-25 11:59:47 +02:00
\fB \- \- insert\- ignore\fR
.sp
Write
2010-04-28 15:06:11 +02:00
INSERT IGNORE
statements rather than
2009-05-25 11:59:47 +02:00
INSERT
2010-04-28 15:06:11 +02:00
statements\& .
2009-09-16 14:03:18 +02:00
.RE
.sp
.RS 4
.ie n \{ \
\h '-04'\(bu \h '+03'\c
. \}
.el \{ \
.sp -1
.IP \(bu 2 .3
. \}
2024-09-03 19:15:59 +02:00
. \" mariadb-dump: lines-terminated-by option
. \" lines-terminated-by option: mariadb-dump
2009-09-16 14:03:18 +02:00
\fB \- \- lines\- terminated\- by=\& .\& .\& .\fR
2009-05-25 11:59:47 +02:00
.sp
This option is used with the
2010-04-28 15:06:11 +02:00
\fB \- \- tab\fR
option and has the same meaning as the corresponding
LINES
clause for
2015-09-09 14:32:52 +02:00
LOAD DATA INFILE\& .
2009-09-16 14:03:18 +02:00
.RE
.sp
.RS 4
.ie n \{ \
\h '-04'\(bu \h '+03'\c
. \}
.el \{ \
.sp -1
.IP \(bu 2 .3
. \}
2024-09-03 19:15:59 +02:00
. \" mariadb-dump: lock-all-tables option
. \" lock-all-tables option: mariadb-dump
2009-05-25 11:59:47 +02:00
\fB \- \- lock\- all\- tables\fR ,
\fB \- x\fR
.sp
2009-09-16 14:03:18 +02:00
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
2009-05-25 11:59:47 +02:00
\fB \- \- single\- transaction\fR
and
2009-09-16 14:03:18 +02:00
\fB \- \- lock\- tables\fR \& .
.RE
.sp
.RS 4
.ie n \{ \
\h '-04'\(bu \h '+03'\c
. \}
.el \{ \
.sp -1
.IP \(bu 2 .3
. \}
2024-09-03 19:15:59 +02:00
. \" mariadb-dump: lock-tables option
. \" lock-tables option: mariadb-dump
2009-05-25 11:59:47 +02:00
\fB \- \- lock\- tables\fR ,
\fB \- l\fR
.sp
2010-04-28 15:06:11 +02:00
For each dumped database, lock all tables to be dumped before dumping them\& . The tables are locked with
2009-05-25 11:59:47 +02:00
READ LOCAL
to allow concurrent inserts in the case of
MyISAM
2009-09-16 14:03:18 +02:00
tables\& . For transactional tables such as
InnoDB,
2009-05-25 11:59:47 +02:00
\fB \- \- single\- transaction\fR
2010-04-28 15:06:11 +02:00
is a much better option than
\fB \- \- lock\- tables\fR
because it does not need to lock the tables at all\& .
2009-05-25 11:59:47 +02:00
.sp
2010-04-28 15:06:11 +02:00
Because
2009-05-25 11:59:47 +02:00
\fB \- \- lock\- tables\fR
2010-04-28 15:06:11 +02:00
locks tables for each database separately, 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\& .
2015-09-09 14:32:52 +02:00
.sp
Use \fB --skip-lock-tables\fR to disable\& .
2009-09-16 14:03:18 +02:00
.RE
.sp
.RS 4
.ie n \{ \
\h '-04'\(bu \h '+03'\c
. \}
.el \{ \
.sp -1
.IP \(bu 2 .3
. \}
2024-09-03 19:15:59 +02:00
. \" mariadb-dump: log-error option
. \" log-error option: mariadb-dump
2009-05-25 11:59:47 +02:00
\fB \- \- log\- error=\fR \fB \fI file_name\fR \fR
.sp
2015-09-09 14:32:52 +02:00
Log warnings and errors by appending them to the named file\& . The default is to do no logging\& .
2009-09-16 14:03:18 +02:00
.RE
.sp
.RS 4
.ie n \{ \
\h '-04'\(bu \h '+03'\c
. \}
.el \{ \
2015-12-14 23:16:27 +02:00
.sp -1
.IP \(bu 2 .3
. \}
2024-09-03 19:15:59 +02:00
. \" mariadb-dump: log-queries option
. \" log-queries option: mariadb-dump
2015-12-14 23:16:27 +02:00
\fB \- \- log\- queries\fR \fR
.sp
MDEV-23789: Fix unnecessary acute accents in man pages
The man pages has several places where \' is intended to escape the single
quote and just print '. However, in reality this will print an ` (acute
accent). Fix this by removing excess backslashes. Also remove some excess
& in front of dots, such escaping is also unnecessary.
Also join several lines to avoid lone words in quotes to be read by groff
as macros when they are just text.
In a table (t{}) the content must be on new lines separately, so groff
will try to read them as macros too, so use \(aq that renders to '
(single quote).
This error was originally detected by Lintian:
https://lintian.debian.org/tags/acute-accent-in-manual-page
Example of man page sections before and after:
Make a backup of each table´s data file using the name tbl_name.OLD.
->
Make a backup of each table's data file using the name tbl_name.OLD.
A typical debug_options string is ´d:t:o,file_name´.
The default is ´d:t:o,/tmp/my_print_defaults.trace´.
->
A typical debug_options string is 'd:t:o,file_name'.
The default is 'd:t:o,/tmp/my_print_defaults.trace'.
shell> mysql --xml -uroot -e "SHOW VARIABLES LIKE ´version%´"
<?xml version="1.0"?>
<resultset statement="SHOW VARIABLES LIKE ´version%´" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
->
shell> mysql --xml -uroot -e "SHOW VARIABLES LIKE 'version%'"
<?xml version="1.0"?>
<resultset statement="SHOW VARIABLES LIKE 'version%'" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
This command was used to validate no man pages have syntax errors:
for x in *.?
do
echo "##### $x #####"
LC_ALL=C.UTF-8 MANROFFSEQ='' MANWIDTH=80 man --warnings -E UTF-8 -l -Tutf8 -Z $x >/dev/null
done
The man pages are not perfect after this, there are still a lot of
suboptimal syntax, but this helps towards better man pages.
All new code of the whole pull request, including one or several files
that are either new files or modified ones, are contributed under the
BSD-new license. I am contributing on behalf of my employer Amazon Web
Services, Inc.
2023-03-11 13:01:39 -08:00
When restoring the dump, the server will, if logging is turned on, log the queries to the general and slow query log\& .
2015-12-14 23:16:27 +02:00
Defaults to on; use \fB --skip-log-queries\fR to disable\& .
.RE
.sp
.RS 4
.ie n \{ \
\h '-04'\(bu \h '+03'\c
. \}
.el \{ \
2009-09-16 14:03:18 +02:00
.sp -1
.IP \(bu 2 .3
. \}
2024-09-03 19:15:59 +02:00
. \" mariadb-dump: master-data option
. \" master-data option: mariadb-dump
2009-05-25 11:59:47 +02:00
\fB \- \- master\- data[=\fR \fB \fI value\fR \fR \fB ]\fR
.sp
2009-09-16 14:03:18 +02:00
Use this option to dump a master replication server to produce a dump file that can be used to set up another server as a slave of the master\& . It causes the dump output to include a
2009-05-25 11:59:47 +02:00
CHANGE MASTER TO
2010-04-28 15:06:11 +02:00
statement that indicates the binary log coordinates (file name and position) of the dumped server\& . These are the master server coordinates from which the slave should start replicating after you load the dump file into the slave\& .
2009-05-25 11:59:47 +02:00
.sp
If the option value is 2, the
CHANGE MASTER TO
2010-04-28 15:06:11 +02:00
statement is written as an SQL comment, and thus is informative only; it has no effect when the dump file is reloaded\& . If the option value is 1, the statement is not written as a comment and takes effect when the dump file is reloaded\& . If no option value is specified, the default value is 1\& .
2009-05-25 11:59:47 +02:00
.sp
This option requires the
RELOAD
2009-09-16 14:03:18 +02:00
privilege and the binary log must be enabled\& .
2009-05-25 11:59:47 +02:00
.sp
The
\fB \- \- master\- data\fR
option automatically turns off
2009-09-16 14:03:18 +02:00
\fB \- \- lock\- tables\fR \& . It also turns on
2009-05-25 11:59:47 +02:00
\fB \- \- lock\- all\- tables\fR , unless
\fB \- \- single\- transaction\fR
2015-09-09 14:32:52 +02:00
also is specified\& . In all cases, any action on logs happens at the exact moment of the dump\& .
2009-09-16 14:03:18 +02:00
.sp
It is also possible to set up a slave by dumping an existing slave of the master\& . To do this, use the following procedure on the existing slave:
.sp
.RS 4
.ie n \{ \
\h '-04' 1.\h '+01'\c
. \}
.el \{ \
.sp -1
.IP " 1." 4 .2
. \}
MDEV-23789: Fix unnecessary acute accents in man pages
The man pages has several places where \' is intended to escape the single
quote and just print '. However, in reality this will print an ` (acute
accent). Fix this by removing excess backslashes. Also remove some excess
& in front of dots, such escaping is also unnecessary.
Also join several lines to avoid lone words in quotes to be read by groff
as macros when they are just text.
In a table (t{}) the content must be on new lines separately, so groff
will try to read them as macros too, so use \(aq that renders to '
(single quote).
This error was originally detected by Lintian:
https://lintian.debian.org/tags/acute-accent-in-manual-page
Example of man page sections before and after:
Make a backup of each table´s data file using the name tbl_name.OLD.
->
Make a backup of each table's data file using the name tbl_name.OLD.
A typical debug_options string is ´d:t:o,file_name´.
The default is ´d:t:o,/tmp/my_print_defaults.trace´.
->
A typical debug_options string is 'd:t:o,file_name'.
The default is 'd:t:o,/tmp/my_print_defaults.trace'.
shell> mysql --xml -uroot -e "SHOW VARIABLES LIKE ´version%´"
<?xml version="1.0"?>
<resultset statement="SHOW VARIABLES LIKE ´version%´" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
->
shell> mysql --xml -uroot -e "SHOW VARIABLES LIKE 'version%'"
<?xml version="1.0"?>
<resultset statement="SHOW VARIABLES LIKE 'version%'" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
This command was used to validate no man pages have syntax errors:
for x in *.?
do
echo "##### $x #####"
LC_ALL=C.UTF-8 MANROFFSEQ='' MANWIDTH=80 man --warnings -E UTF-8 -l -Tutf8 -Z $x >/dev/null
done
The man pages are not perfect after this, there are still a lot of
suboptimal syntax, but this helps towards better man pages.
All new code of the whole pull request, including one or several files
that are either new files or modified ones, are contributed under the
BSD-new license. I am contributing on behalf of my employer Amazon Web
Services, Inc.
2023-03-11 13:01:39 -08:00
Stop the slave's SQL thread and get its current status:
2009-09-16 14:03:18 +02:00
.sp
.if n \{ \
.RS 4
. \}
2009-05-25 11:59:47 +02:00
.nf
2024-09-03 19:15:59 +02:00
mariadb> \fB STOP SLAVE SQL_THREAD;\fR
mariadb> \fB SHOW SLAVE STATUS;\fR
2009-05-25 11:59:47 +02:00
.fi
2009-09-16 14:03:18 +02:00
.if n \{ \
.RE
. \}
.RE
.sp
.RS 4
.ie n \{ \
\h '-04' 2.\h '+01'\c
. \}
.el \{ \
.sp -1
.IP " 2." 4 .2
. \}
2010-04-28 15:06:11 +02:00
From the output of the
SHOW SLAVE STATUS
statement, the binary log coordinates of the master server from which the new slave should start replicating are the values of the
Relay_Master_Log_File
and
Exec_Master_Log_Pos
fields\& . Denote those values as
\fI file_name\fR
and
\fI file_pos\fR \& .
2009-05-25 11:59:47 +02:00
.RE
2009-09-16 14:03:18 +02:00
.sp
.RS 4
.ie n \{ \
\h '-04' 3.\h '+01'\c
. \}
.el \{ \
.sp -1
.IP " 3." 4 .2
. \}
2009-05-25 11:59:47 +02:00
Dump the slave server:
.sp
2009-09-16 14:03:18 +02:00
.if n \{ \
.RS 4
. \}
2009-05-25 11:59:47 +02:00
.nf
2024-09-03 19:15:59 +02:00
shell> \fB mariadb-dump \- \- master\- data=2 \- \- all\- databases > dumpfile\fR
2009-05-25 11:59:47 +02:00
.fi
2009-09-16 14:03:18 +02:00
.if n \{ \
.RE
. \}
2009-05-25 11:59:47 +02:00
.RE
2009-09-16 14:03:18 +02:00
.sp
.RS 4
.ie n \{ \
\h '-04' 4.\h '+01'\c
. \}
.el \{ \
.sp -1
.IP " 4." 4 .2
. \}
2009-05-25 11:59:47 +02:00
Restart the slave:
.sp
2009-09-16 14:03:18 +02:00
.if n \{ \
.RS 4
. \}
2009-05-25 11:59:47 +02:00
.nf
2024-09-03 19:15:59 +02:00
mariadb> \fB START SLAVE;\fR
2009-05-25 11:59:47 +02:00
.fi
2009-09-16 14:03:18 +02:00
.if n \{ \
.RE
. \}
2009-05-25 11:59:47 +02:00
.RE
2009-09-16 14:03:18 +02:00
.sp
.RS 4
.ie n \{ \
\h '-04' 5.\h '+01'\c
. \}
.el \{ \
.sp -1
.IP " 5." 4 .2
. \}
2010-04-28 15:06:11 +02:00
On the new slave, load the dump file:
2009-05-25 11:59:47 +02:00
.sp
2009-09-16 14:03:18 +02:00
.if n \{ \
.RS 4
. \}
2009-05-25 11:59:47 +02:00
.nf
2024-09-03 19:15:59 +02:00
shell> \fB mariadb < dumpfile\fR
2009-05-25 11:59:47 +02:00
.fi
2009-09-16 14:03:18 +02:00
.if n \{ \
2009-05-25 11:59:47 +02:00
.RE
2009-09-16 14:03:18 +02:00
. \}
.RE
.sp
.RS 4
.ie n \{ \
\h '-04' 6.\h '+01'\c
. \}
.el \{ \
.sp -1
.IP " 6." 4 .2
. \}
2009-05-25 11:59:47 +02:00
On the new slave, set the replication coordinates to those of the master server obtained earlier:
.sp
2009-09-16 14:03:18 +02:00
.if n \{ \
.RS 4
. \}
2009-05-25 11:59:47 +02:00
.nf
2024-09-03 19:15:59 +02:00
mariadb> \fB CHANGE MASTER TO\fR
MDEV-23789: Fix unnecessary acute accents in man pages
The man pages has several places where \' is intended to escape the single
quote and just print '. However, in reality this will print an ` (acute
accent). Fix this by removing excess backslashes. Also remove some excess
& in front of dots, such escaping is also unnecessary.
Also join several lines to avoid lone words in quotes to be read by groff
as macros when they are just text.
In a table (t{}) the content must be on new lines separately, so groff
will try to read them as macros too, so use \(aq that renders to '
(single quote).
This error was originally detected by Lintian:
https://lintian.debian.org/tags/acute-accent-in-manual-page
Example of man page sections before and after:
Make a backup of each table´s data file using the name tbl_name.OLD.
->
Make a backup of each table's data file using the name tbl_name.OLD.
A typical debug_options string is ´d:t:o,file_name´.
The default is ´d:t:o,/tmp/my_print_defaults.trace´.
->
A typical debug_options string is 'd:t:o,file_name'.
The default is 'd:t:o,/tmp/my_print_defaults.trace'.
shell> mysql --xml -uroot -e "SHOW VARIABLES LIKE ´version%´"
<?xml version="1.0"?>
<resultset statement="SHOW VARIABLES LIKE ´version%´" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
->
shell> mysql --xml -uroot -e "SHOW VARIABLES LIKE 'version%'"
<?xml version="1.0"?>
<resultset statement="SHOW VARIABLES LIKE 'version%'" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
This command was used to validate no man pages have syntax errors:
for x in *.?
do
echo "##### $x #####"
LC_ALL=C.UTF-8 MANROFFSEQ='' MANWIDTH=80 man --warnings -E UTF-8 -l -Tutf8 -Z $x >/dev/null
done
The man pages are not perfect after this, there are still a lot of
suboptimal syntax, but this helps towards better man pages.
All new code of the whole pull request, including one or several files
that are either new files or modified ones, are contributed under the
BSD-new license. I am contributing on behalf of my employer Amazon Web
Services, Inc.
2023-03-11 13:01:39 -08:00
\- > \fB MASTER_LOG_FILE = '\fR \fB \fI file_name\fR \fR \fB ', MASTER_LOG_POS = \fR \fB \fI file_pos\fR \fR \fB ;\fR
2009-05-25 11:59:47 +02:00
.fi
2009-09-16 14:03:18 +02:00
.if n \{ \
2009-05-25 11:59:47 +02:00
.RE
2009-09-16 14:03:18 +02:00
. \}
.sp
2009-05-25 11:59:47 +02:00
The
CHANGE MASTER TO
statement might also need other parameters, such as
MASTER_HOST
2009-09-16 14:03:18 +02:00
to point the slave to the correct master server host\& . Add any such parameters as necessary\& .
.RE
2009-05-25 11:59:47 +02:00
.RE
2009-09-16 14:03:18 +02:00
.sp
.RS 4
.ie n \{ \
\h '-04'\(bu \h '+03'\c
. \}
.el \{ \
.sp -1
.IP \(bu 2 .3
. \}
2024-09-03 19:15:59 +02:00
. \" mariadb-dump: max-allowed-packet option
. \" max-allowed-packet option: mariadb-dump
2013-06-13 00:13:23 +02:00
\fB \- \- max\- allowed\- packet=\fR \fB \fI length\fR \fR
.sp
2015-12-09 18:22:38 +01:00
Sets the maximum packet length to send to or receive from server\& .
2013-06-13 00:13:23 +02:00
.RE
.sp
.RS 4
.ie n \{ \
\h '-04'\(bu \h '+03'\c
. \}
.el \{ \
.sp -1
.IP \(bu 2 .3
. \}
2024-09-03 19:15:59 +02:00
. \" mariadb-dump: max-statement-time option
. \" max-statement-time option: mariadb-dump
2022-07-29 16:07:42 +10:00
\fB \- \- max\- statement\- time=\fR \fB \fI seconds\fR \fR
.sp
Sets the maximum time any statement can run before being timed out by the server. (Default value is 0 (no limit))\&
.RE
.sp
.RS 4
.ie n \{ \
\h '-04'\(bu \h '+03'\c
. \}
.el \{ \
.sp -1
.IP \(bu 2 .3
. \}
2024-09-03 19:15:59 +02:00
. \" mariadb-dump: net-buffer-length option
. \" net-buffer-length option: mariadb-dump
2013-06-13 00:13:23 +02:00
\fB \- \- net\- buffer\- length=\fR \fB \fI length\fR \fR
.sp
Sets the buffer size for TCP/IP and socket communication\& .
.RE
.sp
.RS 4
.ie n \{ \
\h '-04'\(bu \h '+03'\c
. \}
.el \{ \
.sp -1
.IP \(bu 2 .3
. \}
2024-09-03 19:15:59 +02:00
. \" mariadb-dump: no-autocommit option
. \" no-autocommit option: mariadb-dump
2009-05-25 11:59:47 +02:00
\fB \- \- no\- autocommit\fR
.sp
Enclose the
INSERT
statements for each dumped table within
SET autocommit = 0
and
COMMIT
2009-09-16 14:03:18 +02:00
statements\& .
.RE
.sp
.RS 4
.ie n \{ \
\h '-04'\(bu \h '+03'\c
. \}
.el \{ \
.sp -1
.IP \(bu 2 .3
. \}
2024-09-03 19:15:59 +02:00
. \" mariadb-dump: no-create-db option
. \" no-create-db option: mariadb-dump
2009-05-25 11:59:47 +02:00
\fB \- \- no\- create\- db\fR ,
\fB \- n\fR
.sp
This option suppresses the
CREATE DATABASE
statements that are otherwise included in the output if the
\fB \- \- databases\fR
or
\fB \- \- all\- databases\fR
2009-09-16 14:03:18 +02:00
option is given\& .
.RE
.sp
.RS 4
.ie n \{ \
\h '-04'\(bu \h '+03'\c
. \}
.el \{ \
.sp -1
.IP \(bu 2 .3
. \}
2024-09-03 19:15:59 +02:00
. \" mariadb-dump: no-create-info option
. \" no-create-info option: mariadb-dump
2009-05-25 11:59:47 +02:00
\fB \- \- no\- create\- info\fR ,
\fB \- t\fR
.sp
Do not write
CREATE TABLE
2009-09-16 14:03:18 +02:00
statements that re\- create each dumped table\& .
.RE
.sp
.RS 4
.ie n \{ \
\h '-04'\(bu \h '+03'\c
. \}
.el \{ \
.sp -1
.IP \(bu 2 .3
. \}
2024-09-03 19:15:59 +02:00
. \" mariadb-dump: no-data option
. \" no-data option: mariadb-dump
2009-05-25 11:59:47 +02:00
\fB \- \- no\- data\fR ,
\fB \- d\fR
.sp
2010-04-28 15:06:11 +02:00
Do not write any table row information (that is, do not dump table contents)\& . This is useful if you want to dump only the
2009-05-25 11:59:47 +02:00
CREATE TABLE
2010-04-28 15:06:11 +02:00
statement for the table (for example, to create an empty copy of the table by loading the dump file)\& .
2009-09-16 14:03:18 +02:00
.RE
.sp
.RS 4
.ie n \{ \
\h '-04'\(bu \h '+03'\c
. \}
.el \{ \
.sp -1
.IP \(bu 2 .3
. \}
2024-09-03 19:15:59 +02:00
. \" mariadb-dump: no-defaults option
. \" no-defaults option: mariadb-dump
2013-06-13 00:13:23 +02:00
\fB \- \- no\- defaults\fR
.sp
Do not read default options from any option file\& . This must be given as the first argument\& .
.RE
.sp
.RS 4
.ie n \{ \
\h '-04'\(bu \h '+03'\c
. \}
.el \{ \
.sp -1
.IP \(bu 2 .3
. \}
2024-09-03 19:15:59 +02:00
. \" mariadb-dump: no-set-names option
. \" no-set-names option: mariadb-dump
2010-04-28 15:06:11 +02:00
\fB \- \- no\- set\- names\fR ,
\fB \- N\fR
2009-09-16 14:03:18 +02:00
.sp
2010-04-28 15:06:11 +02:00
This has the same effect as
\fB \- \- skip\- set\- charset\fR \& .
2009-09-16 14:03:18 +02:00
.RE
.sp
.RS 4
.ie n \{ \
\h '-04'\(bu \h '+03'\c
. \}
.el \{ \
.sp -1
.IP \(bu 2 .3
. \}
2024-09-03 19:15:59 +02:00
. \" mariadb-dump: opt option
. \" opt option: mariadb-dump
2009-05-25 11:59:47 +02:00
\fB \- \- opt\fR
.sp
2010-04-28 15:06:11 +02:00
This option is shorthand\& . It is the same as specifying
2009-05-25 11:59:47 +02:00
\fB \- \- add\- drop\- table\fR
\fB \- \- add\- locks\fR
\fB \- \- create\- options\fR
\fB \- \- disable\- keys\fR
\fB \- \- extended\- insert\fR
\fB \- \- lock\- tables\fR
\fB \- \- quick\fR
2015-09-09 14:32:52 +02:00
\fB \- \- set\- charset\fR \& . It should give you a fast dump operation and produce a dump file that can be reloaded into a MariaDB server quickly\& .
2009-05-25 11:59:47 +02:00
.sp
2024-07-16 14:41:56 +02:00
The \fB \- \- opt\fR option is enabled by default\& . Use \fB \- \- skip\- opt\fR to disable it\& .
2010-04-28 15:06:11 +02:00
See the discussion at the beginning of this section for information about selectively enabling or disabling a subset of the options affected by
2009-09-16 14:03:18 +02:00
\fB \- \- opt\fR \& .
.RE
.sp
.RS 4
.ie n \{ \
\h '-04'\(bu \h '+03'\c
. \}
.el \{ \
.sp -1
.IP \(bu 2 .3
. \}
2024-09-03 19:15:59 +02:00
. \" mariadb-dump: order-by-primary option
. \" order-by-primary option: mariadb-dump
2009-05-25 11:59:47 +02:00
\fB \- \- order\- by\- primary\fR
.sp
MDEV-23789: Fix unnecessary acute accents in man pages
The man pages has several places where \' is intended to escape the single
quote and just print '. However, in reality this will print an ` (acute
accent). Fix this by removing excess backslashes. Also remove some excess
& in front of dots, such escaping is also unnecessary.
Also join several lines to avoid lone words in quotes to be read by groff
as macros when they are just text.
In a table (t{}) the content must be on new lines separately, so groff
will try to read them as macros too, so use \(aq that renders to '
(single quote).
This error was originally detected by Lintian:
https://lintian.debian.org/tags/acute-accent-in-manual-page
Example of man page sections before and after:
Make a backup of each table´s data file using the name tbl_name.OLD.
->
Make a backup of each table's data file using the name tbl_name.OLD.
A typical debug_options string is ´d:t:o,file_name´.
The default is ´d:t:o,/tmp/my_print_defaults.trace´.
->
A typical debug_options string is 'd:t:o,file_name'.
The default is 'd:t:o,/tmp/my_print_defaults.trace'.
shell> mysql --xml -uroot -e "SHOW VARIABLES LIKE ´version%´"
<?xml version="1.0"?>
<resultset statement="SHOW VARIABLES LIKE ´version%´" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
->
shell> mysql --xml -uroot -e "SHOW VARIABLES LIKE 'version%'"
<?xml version="1.0"?>
<resultset statement="SHOW VARIABLES LIKE 'version%'" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
This command was used to validate no man pages have syntax errors:
for x in *.?
do
echo "##### $x #####"
LC_ALL=C.UTF-8 MANROFFSEQ='' MANWIDTH=80 man --warnings -E UTF-8 -l -Tutf8 -Z $x >/dev/null
done
The man pages are not perfect after this, there are still a lot of
suboptimal syntax, but this helps towards better man pages.
All new code of the whole pull request, including one or several files
that are either new files or modified ones, are contributed under the
BSD-new license. I am contributing on behalf of my employer Amazon Web
Services, Inc.
2023-03-11 13:01:39 -08:00
Dump each table's rows sorted by its primary key, or by its first unique index, if such an index exists\& . This is useful when dumping a
2009-05-25 11:59:47 +02:00
MyISAM
table to be loaded into an
InnoDB
2010-04-28 15:06:11 +02:00
table, but will make the dump operation take considerably longer\& .
2009-09-16 14:03:18 +02:00
.RE
.sp
.RS 4
.ie n \{ \
\h '-04'\(bu \h '+03'\c
. \}
.el \{ \
.sp -1
.IP \(bu 2 .3
. \}
2024-09-03 19:15:59 +02:00
. \" mariadb-dump: order-by-size option
. \" order-by-size option: mariadb-dump
2024-07-16 14:41:56 +02:00
\fB \- \- order\- by\- size\fR
.sp
Dump each table according to their size, smallest first. Useful when using \- \- single-transaction on tables
which get truncated/altered often\& . The assumption here is that smaller tables get truncated more often,
and by dumping those first, this reduces the chance that a \- \- single-transaction dump will fail with with
'Table definition has changed, please retry transaction'\& .
.RE
.sp
.RS 4
.ie n \{ \
\h '-04'\(bu \h '+03'\c
. \}
.el \{ \
.sp -1
.IP \(bu 2 .3
. \}
2024-09-03 19:15:59 +02:00
. \" mariadb-dump: parallel option
. \" parallel option: mariadb-dump
2024-07-16 14:41:56 +02:00
\fB \- \- parallel=#\fR ,
\fB \- j\fR
.sp
Number of dump table jobs executed in parallel (only for use with the \- \- tab option). Initial testing
indicates that performance can be increased (dump time decreased) up to 4 times on smaller size dumps,
when the database fits into memory. There is a point at which disk becomes the bottleneck, after which
adding more parallel jobs does not bring better performance.
.RE
.sp
.RS 4
.ie n \{ \
\h '-04'\(bu \h '+03'\c
. \}
.el \{ \
.sp -1
.IP \(bu 2 .3
. \}
2024-09-03 19:15:59 +02:00
. \" mariadb-dump: password option
. \" password option: mariadb-dump
2009-05-25 11:59:47 +02:00
\fB \- \- password[=\fR \fB \fI password\fR \fR \fB ]\fR ,
\fB \- p[\fR \fB \fI password\fR \fR \fB ]\fR
.sp
2009-09-16 14:03:18 +02:00
The password to use when connecting to the server\& . If you use the short option form (\fB \- p\fR ), you
2009-05-25 11:59:47 +02:00
\fI cannot\fR
2009-09-16 14:03:18 +02:00
have a space between the option and the password\& . If you omit the
2009-05-25 11:59:47 +02:00
\fI password\fR
value following the
\fB \- \- password\fR
or
\fB \- p\fR
2010-04-28 15:06:11 +02:00
option on the command line,
2024-09-03 19:15:59 +02:00
\fB mariadb-dump\fR
2010-04-28 15:06:11 +02:00
prompts for one\& .
2009-05-25 11:59:47 +02:00
.sp
2015-09-09 14:32:52 +02:00
Specifying a password on the command line should be considered insecure\& . You can use an option file to avoid giving the password on the command line\& .
2009-09-16 14:03:18 +02:00
.RE
.sp
.RS 4
.ie n \{ \
\h '-04'\(bu \h '+03'\c
. \}
.el \{ \
.sp -1
.IP \(bu 2 .3
. \}
2024-09-03 19:15:59 +02:00
. \" mariadb-dump: pipe option
. \" pipe option: mariadb-dump
2009-05-25 11:59:47 +02:00
\fB \- \- pipe\fR ,
\fB \- W\fR
.sp
2010-04-28 15:06:11 +02:00
On Windows, connect to the server via a named pipe\& . This option applies only if the server supports named\- pipe connections\& .
2009-09-16 14:03:18 +02:00
.RE
.sp
.RS 4
.ie n \{ \
\h '-04'\(bu \h '+03'\c
. \}
.el \{ \
.sp -1
.IP \(bu 2 .3
. \}
2024-09-03 19:15:59 +02:00
. \" mariadb-dump: plugin-dir option
. \" plugin-dir option: mariadb-dump
2015-09-09 14:32:52 +02:00
\fB \- \- plugin\- dir\fR
.sp
Directory for client-side plugins\& .
.RE
.sp
.RS 4
.ie n \{ \
\h '-04'\(bu \h '+03'\c
. \}
.el \{ \
.sp -1
.IP \(bu 2 .3
. \}
2024-09-03 19:15:59 +02:00
. \" mariadb-dump: port option
. \" port option: mariadb-dump
2009-05-25 11:59:47 +02:00
\fB \- \- port=\fR \fB \fI port_num\fR \fR ,
\fB \- P \fR \fB \fI port_num\fR \fR
.sp
2009-09-16 14:03:18 +02:00
The TCP/IP port number to use for the connection\& .
2021-05-10 11:10:53 -06:00
Forces --protocol=tcp when specified on the command line without other connection properties\& .
2009-09-16 14:03:18 +02:00
.RE
.sp
.RS 4
.ie n \{ \
\h '-04'\(bu \h '+03'\c
. \}
.el \{ \
.sp -1
.IP \(bu 2 .3
. \}
2024-09-03 19:15:59 +02:00
. \" mariadb-dump: protocol option
. \" protocol option: mariadb-dump
2009-05-25 11:59:47 +02:00
\fB \- \- protocol={TCP|SOCKET|PIPE|MEMORY}\fR
.sp
2015-09-09 14:32:52 +02:00
The connection protocol to use for connecting to the server\& . It is useful when the other connection parameters normally would cause a protocol to be used other than the one you want\& .
2009-09-16 14:03:18 +02:00
.RE
.sp
.RS 4
.ie n \{ \
\h '-04'\(bu \h '+03'\c
. \}
.el \{ \
.sp -1
.IP \(bu 2 .3
. \}
2024-09-03 19:15:59 +02:00
. \" mariadb-dump: quick option
. \" quick option: mariadb-dump
2009-05-25 11:59:47 +02:00
\fB \- \- quick\fR ,
\fB \- q\fR
.sp
2009-09-16 14:03:18 +02:00
This option is useful for dumping large tables\& . It forces
2024-09-03 19:15:59 +02:00
\fB mariadb-dump\fR
2009-09-16 14:03:18 +02:00
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\& .
.RE
.sp
.RS 4
.ie n \{ \
\h '-04'\(bu \h '+03'\c
. \}
.el \{ \
.sp -1
.IP \(bu 2 .3
. \}
2024-09-03 19:15:59 +02:00
. \" mariadb-dump: print-defaults option
. \" print-defaults option: mariadb-dump
2013-06-13 00:13:23 +02:00
\fB \- \- print\- defaults\fR
.sp
2015-09-09 14:32:52 +02:00
Print the program argument list and exit\& . This must be given as the first argument\& .
2013-06-13 00:13:23 +02:00
.RE
.sp
.RS 4
.ie n \{ \
\h '-04'\(bu \h '+03'\c
. \}
.el \{ \
.sp -1
.IP \(bu 2 .3
. \}
2024-09-03 19:15:59 +02:00
. \" mariadb-dump: quote-names option
. \" quote-names option: mariadb-dump
2009-05-25 11:59:47 +02:00
\fB \- \- quote\- names\fR ,
\fB \- Q\fR
.sp
2010-04-28 15:06:11 +02:00
Quote identifiers (such as database, table, and column names) within
2009-05-25 11:59:47 +02:00
\(lq `\(rq
2009-09-16 14:03:18 +02:00
characters\& . If the
2009-05-25 11:59:47 +02:00
ANSI_QUOTES
2010-04-28 15:06:11 +02:00
SQL mode is enabled, identifiers are quoted within
2009-05-25 11:59:47 +02:00
\(lq "\(rq
2009-09-16 14:03:18 +02:00
characters\& . This option is enabled by default\& . It can be disabled with
2009-05-25 11:59:47 +02:00
\fB \- \- skip\- quote\- names\fR , but this option should be given after any option such as
\fB \- \- compatible\fR
that may enable
2009-09-16 14:03:18 +02:00
\fB \- \- quote\- names\fR \& .
.RE
.sp
.RS 4
.ie n \{ \
\h '-04'\(bu \h '+03'\c
. \}
.el \{ \
.sp -1
.IP \(bu 2 .3
. \}
2024-09-03 19:15:59 +02:00
. \" mariadb-dump: replace option
. \" replace option: mariadb-dump
2009-05-25 11:59:47 +02:00
\fB \- \- replace\fR
.sp
Write
REPLACE
statements rather than
INSERT
2015-09-09 14:32:52 +02:00
statements\& .
2009-09-16 14:03:18 +02:00
.RE
.sp
.RS 4
.ie n \{ \
\h '-04'\(bu \h '+03'\c
. \}
.el \{ \
.sp -1
.IP \(bu 2 .3
. \}
2024-09-03 19:15:59 +02:00
. \" mariadb-dump: result-file option
. \" result-file option: mariadb-dump
2009-05-25 11:59:47 +02:00
\fB \- \- result\- file=\fR \fB \fI file_name\fR \fR ,
\fB \- r \fR \fB \fI file_name\fR \fR
.sp
2009-09-16 14:03:18 +02:00
Direct output to a given file\& . This option should be used on Windows to prevent newline
\(lq \e n\(rq
2009-05-25 11:59:47 +02:00
characters from being converted to
2009-09-16 14:03:18 +02:00
\(lq \e r\e n\(rq
2010-04-28 15:06:11 +02:00
carriage return/newline sequences\& . The result file is created and its previous contents overwritten, even if an error occurs while generating the dump\& .
2009-09-16 14:03:18 +02:00
.RE
.sp
.RS 4
.ie n \{ \
\h '-04'\(bu \h '+03'\c
. \}
.el \{ \
.sp -1
.IP \(bu 2 .3
. \}
2024-09-03 19:15:59 +02:00
. \" mariadb-dump: routines option
. \" routines option: mariadb-dump
2009-05-25 11:59:47 +02:00
\fB \- \- routines\fR ,
\fB \- R\fR
.sp
2010-04-28 15:06:11 +02:00
Included stored routines (procedures and functions) for the dumped databases in the output\& . Use of this option requires the
2009-05-25 11:59:47 +02:00
SELECT
privilege for the
2009-09-16 14:03:18 +02:00
mysql\& .proc
table\& . The output generated by using
2009-05-25 11:59:47 +02:00
\fB \- \- routines\fR
contains
CREATE PROCEDURE
and
CREATE FUNCTION
2009-09-16 14:03:18 +02:00
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\& .
2009-05-25 11:59:47 +02:00
.sp
If you require routines to be re\- created with their original timestamp attributes, do not use
2009-09-16 14:03:18 +02:00
\fB \- \- routines\fR \& . Instead, dump and reload the contents of the
mysql\& .proc
2015-09-09 14:32:52 +02:00
table directly, using a MariaDB account that has appropriate privileges for the
2009-05-25 11:59:47 +02:00
mysql
2009-09-16 14:03:18 +02:00
database\& .
2009-05-25 11:59:47 +02:00
.sp
2009-09-16 14:03:18 +02:00
.RE
.sp
.RS 4
.ie n \{ \
\h '-04'\(bu \h '+03'\c
. \}
.el \{ \
.sp -1
.IP \(bu 2 .3
. \}
2024-09-03 19:15:59 +02:00
. \" mariadb-dump: set-charset option
. \" set-charset option: mariadb-dump
2009-05-25 11:59:47 +02:00
\fB \- \- set\- charset\fR
.sp
Add
SET NAMES \fI default_character_set\fR
2009-09-16 14:03:18 +02:00
to the output\& . This option is enabled by default\& . To suppress the
2009-05-25 11:59:47 +02:00
SET NAMES
statement, use
2009-09-16 14:03:18 +02:00
\fB \- \- skip\- set\- charset\fR \& .
.RE
.sp
.RS 4
.ie n \{ \
\h '-04'\(bu \h '+03'\c
. \}
.el \{ \
.sp -1
.IP \(bu 2 .3
. \}
2024-09-03 19:15:59 +02:00
. \" mariadb-dump: single-transaction option
. \" single-transaction option: mariadb-dump
2009-05-25 11:59:47 +02:00
\fB \- \- single\- transaction\fR
.sp
2010-04-28 15:06:11 +02:00
This option sends a
START TRANSACTION
SQL statement to the server before dumping data\& . It is useful only with transactional tables such as
2009-05-25 11:59:47 +02:00
InnoDB, because then it dumps the consistent state of the database at the time when
BEGIN
2009-09-16 14:03:18 +02:00
was issued without blocking any applications\& .
2009-05-25 11:59:47 +02:00
.sp
When using this option, you should keep in mind that only
InnoDB
2009-09-16 14:03:18 +02:00
tables are dumped in a consistent state\& . For example, any
2009-05-25 11:59:47 +02:00
MyISAM
or
MEMORY
2009-09-16 14:03:18 +02:00
tables dumped while using this option may still change state\& .
2009-05-25 11:59:47 +02:00
.sp
While a
\fB \- \- single\- transaction\fR
2010-04-28 15:06:11 +02:00
dump is in process, to ensure a valid dump file (correct table contents and binary log coordinates), no other connection should use the following statements:
2009-05-25 11:59:47 +02:00
ALTER TABLE,
2010-04-28 15:06:11 +02:00
CREATE TABLE,
2009-05-25 11:59:47 +02:00
DROP TABLE,
RENAME TABLE,
2009-09-16 14:03:18 +02:00
TRUNCATE TABLE\& . A consistent read is not isolated from those statements, so use of them on a table to be dumped can cause the
2009-05-25 11:59:47 +02:00
SELECT
2010-04-28 15:06:11 +02:00
that is performed by
2024-09-03 19:15:59 +02:00
\fB mariadb-dump\fR
2009-09-16 14:03:18 +02:00
to retrieve the table contents to obtain incorrect contents or fail\& .
2009-05-25 11:59:47 +02:00
.sp
2010-04-28 15:06:11 +02:00
The
\fB \- \- single\- transaction\fR
option and the
\fB \- \- lock\- tables\fR
option are mutually exclusive because
LOCK TABLES
causes any pending transactions to be committed implicitly\& .
.sp
To dump large tables, you should combine the
2009-05-25 11:59:47 +02:00
\fB \- \- single\- transaction\fR
2010-04-28 15:06:11 +02:00
option with
2009-09-16 14:03:18 +02:00
\fB \- \- quick\fR \& .
.RE
.sp
.RS 4
.ie n \{ \
\h '-04'\(bu \h '+03'\c
. \}
.el \{ \
.sp -1
.IP \(bu 2 .3
. \}
2024-09-03 19:15:59 +02:00
. \" mariadb-dump: skip-add-drop-table option
. \" skip-add-drop-table option: mariadb-dump
2015-09-09 14:32:52 +02:00
\fB \- \- skip\- add\- drop\- table\fR
.sp
MDEV-23789: Fix unnecessary acute accents in man pages
The man pages has several places where \' is intended to escape the single
quote and just print '. However, in reality this will print an ` (acute
accent). Fix this by removing excess backslashes. Also remove some excess
& in front of dots, such escaping is also unnecessary.
Also join several lines to avoid lone words in quotes to be read by groff
as macros when they are just text.
In a table (t{}) the content must be on new lines separately, so groff
will try to read them as macros too, so use \(aq that renders to '
(single quote).
This error was originally detected by Lintian:
https://lintian.debian.org/tags/acute-accent-in-manual-page
Example of man page sections before and after:
Make a backup of each table´s data file using the name tbl_name.OLD.
->
Make a backup of each table's data file using the name tbl_name.OLD.
A typical debug_options string is ´d:t:o,file_name´.
The default is ´d:t:o,/tmp/my_print_defaults.trace´.
->
A typical debug_options string is 'd:t:o,file_name'.
The default is 'd:t:o,/tmp/my_print_defaults.trace'.
shell> mysql --xml -uroot -e "SHOW VARIABLES LIKE ´version%´"
<?xml version="1.0"?>
<resultset statement="SHOW VARIABLES LIKE ´version%´" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
->
shell> mysql --xml -uroot -e "SHOW VARIABLES LIKE 'version%'"
<?xml version="1.0"?>
<resultset statement="SHOW VARIABLES LIKE 'version%'" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
This command was used to validate no man pages have syntax errors:
for x in *.?
do
echo "##### $x #####"
LC_ALL=C.UTF-8 MANROFFSEQ='' MANWIDTH=80 man --warnings -E UTF-8 -l -Tutf8 -Z $x >/dev/null
done
The man pages are not perfect after this, there are still a lot of
suboptimal syntax, but this helps towards better man pages.
All new code of the whole pull request, including one or several files
that are either new files or modified ones, are contributed under the
BSD-new license. I am contributing on behalf of my employer Amazon Web
Services, Inc.
2023-03-11 13:01:39 -08:00
Disable the
2015-09-09 14:32:52 +02:00
\fB \- \- add\- drop\- table\fR
option\& .
.RE
.sp
.RS 4
.ie n \{ \
\h '-04'\(bu \h '+03'\c
. \}
.el \{ \
.sp -1
.IP \(bu 2 .3
. \}
2024-09-03 19:15:59 +02:00
. \" mariadb-dump: skip-add-locks option
. \" skip-add-locks option: mariadb-dump
2015-09-09 14:32:52 +02:00
\fB \- \- skip\- add\- locks\fR
.sp
MDEV-23789: Fix unnecessary acute accents in man pages
The man pages has several places where \' is intended to escape the single
quote and just print '. However, in reality this will print an ` (acute
accent). Fix this by removing excess backslashes. Also remove some excess
& in front of dots, such escaping is also unnecessary.
Also join several lines to avoid lone words in quotes to be read by groff
as macros when they are just text.
In a table (t{}) the content must be on new lines separately, so groff
will try to read them as macros too, so use \(aq that renders to '
(single quote).
This error was originally detected by Lintian:
https://lintian.debian.org/tags/acute-accent-in-manual-page
Example of man page sections before and after:
Make a backup of each table´s data file using the name tbl_name.OLD.
->
Make a backup of each table's data file using the name tbl_name.OLD.
A typical debug_options string is ´d:t:o,file_name´.
The default is ´d:t:o,/tmp/my_print_defaults.trace´.
->
A typical debug_options string is 'd:t:o,file_name'.
The default is 'd:t:o,/tmp/my_print_defaults.trace'.
shell> mysql --xml -uroot -e "SHOW VARIABLES LIKE ´version%´"
<?xml version="1.0"?>
<resultset statement="SHOW VARIABLES LIKE ´version%´" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
->
shell> mysql --xml -uroot -e "SHOW VARIABLES LIKE 'version%'"
<?xml version="1.0"?>
<resultset statement="SHOW VARIABLES LIKE 'version%'" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
This command was used to validate no man pages have syntax errors:
for x in *.?
do
echo "##### $x #####"
LC_ALL=C.UTF-8 MANROFFSEQ='' MANWIDTH=80 man --warnings -E UTF-8 -l -Tutf8 -Z $x >/dev/null
done
The man pages are not perfect after this, there are still a lot of
suboptimal syntax, but this helps towards better man pages.
All new code of the whole pull request, including one or several files
that are either new files or modified ones, are contributed under the
BSD-new license. I am contributing on behalf of my employer Amazon Web
Services, Inc.
2023-03-11 13:01:39 -08:00
Disable the
2015-09-09 14:32:52 +02:00
\fB \- \- add\- locks\fR
option\& .
.RE
.sp
.RS 4
.ie n \{ \
\h '-04'\(bu \h '+03'\c
. \}
.el \{ \
.sp -1
.IP \(bu 2 .3
. \}
2024-09-03 19:15:59 +02:00
. \" mariadb-dump: skip-comments option
. \" skip-comments option: mariadb-dump
2009-05-25 11:59:47 +02:00
\fB \- \- skip\- comments\fR
.sp
MDEV-23789: Fix unnecessary acute accents in man pages
The man pages has several places where \' is intended to escape the single
quote and just print '. However, in reality this will print an ` (acute
accent). Fix this by removing excess backslashes. Also remove some excess
& in front of dots, such escaping is also unnecessary.
Also join several lines to avoid lone words in quotes to be read by groff
as macros when they are just text.
In a table (t{}) the content must be on new lines separately, so groff
will try to read them as macros too, so use \(aq that renders to '
(single quote).
This error was originally detected by Lintian:
https://lintian.debian.org/tags/acute-accent-in-manual-page
Example of man page sections before and after:
Make a backup of each table´s data file using the name tbl_name.OLD.
->
Make a backup of each table's data file using the name tbl_name.OLD.
A typical debug_options string is ´d:t:o,file_name´.
The default is ´d:t:o,/tmp/my_print_defaults.trace´.
->
A typical debug_options string is 'd:t:o,file_name'.
The default is 'd:t:o,/tmp/my_print_defaults.trace'.
shell> mysql --xml -uroot -e "SHOW VARIABLES LIKE ´version%´"
<?xml version="1.0"?>
<resultset statement="SHOW VARIABLES LIKE ´version%´" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
->
shell> mysql --xml -uroot -e "SHOW VARIABLES LIKE 'version%'"
<?xml version="1.0"?>
<resultset statement="SHOW VARIABLES LIKE 'version%'" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
This command was used to validate no man pages have syntax errors:
for x in *.?
do
echo "##### $x #####"
LC_ALL=C.UTF-8 MANROFFSEQ='' MANWIDTH=80 man --warnings -E UTF-8 -l -Tutf8 -Z $x >/dev/null
done
The man pages are not perfect after this, there are still a lot of
suboptimal syntax, but this helps towards better man pages.
All new code of the whole pull request, including one or several files
that are either new files or modified ones, are contributed under the
BSD-new license. I am contributing on behalf of my employer Amazon Web
Services, Inc.
2023-03-11 13:01:39 -08:00
Disable the
2009-05-25 11:59:47 +02:00
\fB \- \- comments\fR
2009-09-16 14:03:18 +02:00
option\& .
.RE
.sp
.RS 4
.ie n \{ \
\h '-04'\(bu \h '+03'\c
. \}
.el \{ \
.sp -1
.IP \(bu 2 .3
. \}
2024-09-03 19:15:59 +02:00
. \" mariadb-dump: skip-compact option
. \" skip-compact option: mariadb-dump
2015-09-09 14:32:52 +02:00
\fB \- \- skip\- compact\fR
.sp
MDEV-23789: Fix unnecessary acute accents in man pages
The man pages has several places where \' is intended to escape the single
quote and just print '. However, in reality this will print an ` (acute
accent). Fix this by removing excess backslashes. Also remove some excess
& in front of dots, such escaping is also unnecessary.
Also join several lines to avoid lone words in quotes to be read by groff
as macros when they are just text.
In a table (t{}) the content must be on new lines separately, so groff
will try to read them as macros too, so use \(aq that renders to '
(single quote).
This error was originally detected by Lintian:
https://lintian.debian.org/tags/acute-accent-in-manual-page
Example of man page sections before and after:
Make a backup of each table´s data file using the name tbl_name.OLD.
->
Make a backup of each table's data file using the name tbl_name.OLD.
A typical debug_options string is ´d:t:o,file_name´.
The default is ´d:t:o,/tmp/my_print_defaults.trace´.
->
A typical debug_options string is 'd:t:o,file_name'.
The default is 'd:t:o,/tmp/my_print_defaults.trace'.
shell> mysql --xml -uroot -e "SHOW VARIABLES LIKE ´version%´"
<?xml version="1.0"?>
<resultset statement="SHOW VARIABLES LIKE ´version%´" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
->
shell> mysql --xml -uroot -e "SHOW VARIABLES LIKE 'version%'"
<?xml version="1.0"?>
<resultset statement="SHOW VARIABLES LIKE 'version%'" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
This command was used to validate no man pages have syntax errors:
for x in *.?
do
echo "##### $x #####"
LC_ALL=C.UTF-8 MANROFFSEQ='' MANWIDTH=80 man --warnings -E UTF-8 -l -Tutf8 -Z $x >/dev/null
done
The man pages are not perfect after this, there are still a lot of
suboptimal syntax, but this helps towards better man pages.
All new code of the whole pull request, including one or several files
that are either new files or modified ones, are contributed under the
BSD-new license. I am contributing on behalf of my employer Amazon Web
Services, Inc.
2023-03-11 13:01:39 -08:00
Disable the
2015-09-09 14:32:52 +02:00
\fB \- \- compact\fR
option\& .
.RE
.sp
.RS 4
.ie n \{ \
\h '-04'\(bu \h '+03'\c
. \}
.el \{ \
.sp -1
.IP \(bu 2 .3
. \}
2024-09-03 19:15:59 +02:00
. \" mariadb-dump: skip-disable-keys option
. \" skip-disable-keys option: mariadb-dump
2015-09-09 14:32:52 +02:00
\fB \- \- skip\- disable\- keys\fR
.sp
MDEV-23789: Fix unnecessary acute accents in man pages
The man pages has several places where \' is intended to escape the single
quote and just print '. However, in reality this will print an ` (acute
accent). Fix this by removing excess backslashes. Also remove some excess
& in front of dots, such escaping is also unnecessary.
Also join several lines to avoid lone words in quotes to be read by groff
as macros when they are just text.
In a table (t{}) the content must be on new lines separately, so groff
will try to read them as macros too, so use \(aq that renders to '
(single quote).
This error was originally detected by Lintian:
https://lintian.debian.org/tags/acute-accent-in-manual-page
Example of man page sections before and after:
Make a backup of each table´s data file using the name tbl_name.OLD.
->
Make a backup of each table's data file using the name tbl_name.OLD.
A typical debug_options string is ´d:t:o,file_name´.
The default is ´d:t:o,/tmp/my_print_defaults.trace´.
->
A typical debug_options string is 'd:t:o,file_name'.
The default is 'd:t:o,/tmp/my_print_defaults.trace'.
shell> mysql --xml -uroot -e "SHOW VARIABLES LIKE ´version%´"
<?xml version="1.0"?>
<resultset statement="SHOW VARIABLES LIKE ´version%´" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
->
shell> mysql --xml -uroot -e "SHOW VARIABLES LIKE 'version%'"
<?xml version="1.0"?>
<resultset statement="SHOW VARIABLES LIKE 'version%'" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
This command was used to validate no man pages have syntax errors:
for x in *.?
do
echo "##### $x #####"
LC_ALL=C.UTF-8 MANROFFSEQ='' MANWIDTH=80 man --warnings -E UTF-8 -l -Tutf8 -Z $x >/dev/null
done
The man pages are not perfect after this, there are still a lot of
suboptimal syntax, but this helps towards better man pages.
All new code of the whole pull request, including one or several files
that are either new files or modified ones, are contributed under the
BSD-new license. I am contributing on behalf of my employer Amazon Web
Services, Inc.
2023-03-11 13:01:39 -08:00
Disable the
2015-09-09 14:32:52 +02:00
\fB \- \- disable\- keys\fR
option\& .
.RE
.sp
.RS 4
.ie n \{ \
\h '-04'\(bu \h '+03'\c
. \}
.el \{ \
.sp -1
.IP \(bu 2 .3
. \}
2024-09-03 19:15:59 +02:00
. \" mariadb-dump: skip-extended-insert option
. \" skip-extended-insert option: mariadb-dump
2015-09-09 14:32:52 +02:00
\fB \- \- skip\- extended\- insert\fR
.sp
MDEV-23789: Fix unnecessary acute accents in man pages
The man pages has several places where \' is intended to escape the single
quote and just print '. However, in reality this will print an ` (acute
accent). Fix this by removing excess backslashes. Also remove some excess
& in front of dots, such escaping is also unnecessary.
Also join several lines to avoid lone words in quotes to be read by groff
as macros when they are just text.
In a table (t{}) the content must be on new lines separately, so groff
will try to read them as macros too, so use \(aq that renders to '
(single quote).
This error was originally detected by Lintian:
https://lintian.debian.org/tags/acute-accent-in-manual-page
Example of man page sections before and after:
Make a backup of each table´s data file using the name tbl_name.OLD.
->
Make a backup of each table's data file using the name tbl_name.OLD.
A typical debug_options string is ´d:t:o,file_name´.
The default is ´d:t:o,/tmp/my_print_defaults.trace´.
->
A typical debug_options string is 'd:t:o,file_name'.
The default is 'd:t:o,/tmp/my_print_defaults.trace'.
shell> mysql --xml -uroot -e "SHOW VARIABLES LIKE ´version%´"
<?xml version="1.0"?>
<resultset statement="SHOW VARIABLES LIKE ´version%´" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
->
shell> mysql --xml -uroot -e "SHOW VARIABLES LIKE 'version%'"
<?xml version="1.0"?>
<resultset statement="SHOW VARIABLES LIKE 'version%'" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
This command was used to validate no man pages have syntax errors:
for x in *.?
do
echo "##### $x #####"
LC_ALL=C.UTF-8 MANROFFSEQ='' MANWIDTH=80 man --warnings -E UTF-8 -l -Tutf8 -Z $x >/dev/null
done
The man pages are not perfect after this, there are still a lot of
suboptimal syntax, but this helps towards better man pages.
All new code of the whole pull request, including one or several files
that are either new files or modified ones, are contributed under the
BSD-new license. I am contributing on behalf of my employer Amazon Web
Services, Inc.
2023-03-11 13:01:39 -08:00
Disable the
2015-09-09 14:32:52 +02:00
\fB \- \- extended\- insert\fR
option\& .
.RE
.sp
.RS 4
.ie n \{ \
\h '-04'\(bu \h '+03'\c
. \}
.el \{ \
.sp -1
.IP \(bu 2 .3
. \}
2024-09-03 19:15:59 +02:00
. \" mariadb-dump: skip-opt option
. \" skip-opt option: mariadb-dump
2009-05-25 11:59:47 +02:00
\fB \- \- skip\- opt\fR
.sp
2015-09-09 14:32:52 +02:00
Disable the
2009-05-25 11:59:47 +02:00
\fB \- \- opt\fR
2009-09-16 14:03:18 +02:00
option\& .
.RE
.sp
.RS 4
.ie n \{ \
\h '-04'\(bu \h '+03'\c
. \}
.el \{ \
.sp -1
.IP \(bu 2 .3
. \}
2024-09-03 19:15:59 +02:00
. \" mariadb-dump: skip-quick option
. \" skip-quick option: mariadb-dump
2015-09-09 14:32:52 +02:00
\fB \- \- skip\- quick\fR
.sp
MDEV-23789: Fix unnecessary acute accents in man pages
The man pages has several places where \' is intended to escape the single
quote and just print '. However, in reality this will print an ` (acute
accent). Fix this by removing excess backslashes. Also remove some excess
& in front of dots, such escaping is also unnecessary.
Also join several lines to avoid lone words in quotes to be read by groff
as macros when they are just text.
In a table (t{}) the content must be on new lines separately, so groff
will try to read them as macros too, so use \(aq that renders to '
(single quote).
This error was originally detected by Lintian:
https://lintian.debian.org/tags/acute-accent-in-manual-page
Example of man page sections before and after:
Make a backup of each table´s data file using the name tbl_name.OLD.
->
Make a backup of each table's data file using the name tbl_name.OLD.
A typical debug_options string is ´d:t:o,file_name´.
The default is ´d:t:o,/tmp/my_print_defaults.trace´.
->
A typical debug_options string is 'd:t:o,file_name'.
The default is 'd:t:o,/tmp/my_print_defaults.trace'.
shell> mysql --xml -uroot -e "SHOW VARIABLES LIKE ´version%´"
<?xml version="1.0"?>
<resultset statement="SHOW VARIABLES LIKE ´version%´" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
->
shell> mysql --xml -uroot -e "SHOW VARIABLES LIKE 'version%'"
<?xml version="1.0"?>
<resultset statement="SHOW VARIABLES LIKE 'version%'" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
This command was used to validate no man pages have syntax errors:
for x in *.?
do
echo "##### $x #####"
LC_ALL=C.UTF-8 MANROFFSEQ='' MANWIDTH=80 man --warnings -E UTF-8 -l -Tutf8 -Z $x >/dev/null
done
The man pages are not perfect after this, there are still a lot of
suboptimal syntax, but this helps towards better man pages.
All new code of the whole pull request, including one or several files
that are either new files or modified ones, are contributed under the
BSD-new license. I am contributing on behalf of my employer Amazon Web
Services, Inc.
2023-03-11 13:01:39 -08:00
Disable the
2015-09-09 14:32:52 +02:00
\fB \- \- quick\fR
option\& .
.RE
.sp
.RS 4
.ie n \{ \
\h '-04'\(bu \h '+03'\c
. \}
.el \{ \
.sp -1
.IP \(bu 2 .3
. \}
2024-09-03 19:15:59 +02:00
. \" mariadb-dump: skip-quote-names option
. \" skip-quote-names option: mariadb-dump
2015-09-09 14:32:52 +02:00
\fB \- \- skip\- quote\- names\fR
.sp
MDEV-23789: Fix unnecessary acute accents in man pages
The man pages has several places where \' is intended to escape the single
quote and just print '. However, in reality this will print an ` (acute
accent). Fix this by removing excess backslashes. Also remove some excess
& in front of dots, such escaping is also unnecessary.
Also join several lines to avoid lone words in quotes to be read by groff
as macros when they are just text.
In a table (t{}) the content must be on new lines separately, so groff
will try to read them as macros too, so use \(aq that renders to '
(single quote).
This error was originally detected by Lintian:
https://lintian.debian.org/tags/acute-accent-in-manual-page
Example of man page sections before and after:
Make a backup of each table´s data file using the name tbl_name.OLD.
->
Make a backup of each table's data file using the name tbl_name.OLD.
A typical debug_options string is ´d:t:o,file_name´.
The default is ´d:t:o,/tmp/my_print_defaults.trace´.
->
A typical debug_options string is 'd:t:o,file_name'.
The default is 'd:t:o,/tmp/my_print_defaults.trace'.
shell> mysql --xml -uroot -e "SHOW VARIABLES LIKE ´version%´"
<?xml version="1.0"?>
<resultset statement="SHOW VARIABLES LIKE ´version%´" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
->
shell> mysql --xml -uroot -e "SHOW VARIABLES LIKE 'version%'"
<?xml version="1.0"?>
<resultset statement="SHOW VARIABLES LIKE 'version%'" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
This command was used to validate no man pages have syntax errors:
for x in *.?
do
echo "##### $x #####"
LC_ALL=C.UTF-8 MANROFFSEQ='' MANWIDTH=80 man --warnings -E UTF-8 -l -Tutf8 -Z $x >/dev/null
done
The man pages are not perfect after this, there are still a lot of
suboptimal syntax, but this helps towards better man pages.
All new code of the whole pull request, including one or several files
that are either new files or modified ones, are contributed under the
BSD-new license. I am contributing on behalf of my employer Amazon Web
Services, Inc.
2023-03-11 13:01:39 -08:00
Disable the
2015-09-09 14:32:52 +02:00
\fB \- \- quote\- names\fR
option\& .
.RE
.sp
.RS 4
.ie n \{ \
\h '-04'\(bu \h '+03'\c
. \}
.el \{ \
.sp -1
.IP \(bu 2 .3
. \}
2024-09-03 19:15:59 +02:00
. \" mariadb-dump: skip-set-charset option
. \" skip-set-charset option: mariadb-dump
2015-09-09 14:32:52 +02:00
\fB \- \- skip\- set\- charset\fR
.sp
MDEV-23789: Fix unnecessary acute accents in man pages
The man pages has several places where \' is intended to escape the single
quote and just print '. However, in reality this will print an ` (acute
accent). Fix this by removing excess backslashes. Also remove some excess
& in front of dots, such escaping is also unnecessary.
Also join several lines to avoid lone words in quotes to be read by groff
as macros when they are just text.
In a table (t{}) the content must be on new lines separately, so groff
will try to read them as macros too, so use \(aq that renders to '
(single quote).
This error was originally detected by Lintian:
https://lintian.debian.org/tags/acute-accent-in-manual-page
Example of man page sections before and after:
Make a backup of each table´s data file using the name tbl_name.OLD.
->
Make a backup of each table's data file using the name tbl_name.OLD.
A typical debug_options string is ´d:t:o,file_name´.
The default is ´d:t:o,/tmp/my_print_defaults.trace´.
->
A typical debug_options string is 'd:t:o,file_name'.
The default is 'd:t:o,/tmp/my_print_defaults.trace'.
shell> mysql --xml -uroot -e "SHOW VARIABLES LIKE ´version%´"
<?xml version="1.0"?>
<resultset statement="SHOW VARIABLES LIKE ´version%´" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
->
shell> mysql --xml -uroot -e "SHOW VARIABLES LIKE 'version%'"
<?xml version="1.0"?>
<resultset statement="SHOW VARIABLES LIKE 'version%'" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
This command was used to validate no man pages have syntax errors:
for x in *.?
do
echo "##### $x #####"
LC_ALL=C.UTF-8 MANROFFSEQ='' MANWIDTH=80 man --warnings -E UTF-8 -l -Tutf8 -Z $x >/dev/null
done
The man pages are not perfect after this, there are still a lot of
suboptimal syntax, but this helps towards better man pages.
All new code of the whole pull request, including one or several files
that are either new files or modified ones, are contributed under the
BSD-new license. I am contributing on behalf of my employer Amazon Web
Services, Inc.
2023-03-11 13:01:39 -08:00
Disable the
2015-09-09 14:32:52 +02:00
\fB \- \- set\- charset\fR
option\& .
.RE
.sp
.RS 4
.ie n \{ \
\h '-04'\(bu \h '+03'\c
. \}
.el \{ \
.sp -1
.IP \(bu 2 .3
. \}
2024-09-03 19:15:59 +02:00
. \" mariadb-dump: skip-triggers option
. \" skip-triggers option: mariadb-dump
2015-09-09 14:32:52 +02:00
\fB \- \- skip\- triggers\fR
.sp
MDEV-23789: Fix unnecessary acute accents in man pages
The man pages has several places where \' is intended to escape the single
quote and just print '. However, in reality this will print an ` (acute
accent). Fix this by removing excess backslashes. Also remove some excess
& in front of dots, such escaping is also unnecessary.
Also join several lines to avoid lone words in quotes to be read by groff
as macros when they are just text.
In a table (t{}) the content must be on new lines separately, so groff
will try to read them as macros too, so use \(aq that renders to '
(single quote).
This error was originally detected by Lintian:
https://lintian.debian.org/tags/acute-accent-in-manual-page
Example of man page sections before and after:
Make a backup of each table´s data file using the name tbl_name.OLD.
->
Make a backup of each table's data file using the name tbl_name.OLD.
A typical debug_options string is ´d:t:o,file_name´.
The default is ´d:t:o,/tmp/my_print_defaults.trace´.
->
A typical debug_options string is 'd:t:o,file_name'.
The default is 'd:t:o,/tmp/my_print_defaults.trace'.
shell> mysql --xml -uroot -e "SHOW VARIABLES LIKE ´version%´"
<?xml version="1.0"?>
<resultset statement="SHOW VARIABLES LIKE ´version%´" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
->
shell> mysql --xml -uroot -e "SHOW VARIABLES LIKE 'version%'"
<?xml version="1.0"?>
<resultset statement="SHOW VARIABLES LIKE 'version%'" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
This command was used to validate no man pages have syntax errors:
for x in *.?
do
echo "##### $x #####"
LC_ALL=C.UTF-8 MANROFFSEQ='' MANWIDTH=80 man --warnings -E UTF-8 -l -Tutf8 -Z $x >/dev/null
done
The man pages are not perfect after this, there are still a lot of
suboptimal syntax, but this helps towards better man pages.
All new code of the whole pull request, including one or several files
that are either new files or modified ones, are contributed under the
BSD-new license. I am contributing on behalf of my employer Amazon Web
Services, Inc.
2023-03-11 13:01:39 -08:00
Disable the
2015-09-09 14:32:52 +02:00
\fB \- \- triggers\fR
option\& .
.RE
.sp
.RS 4
.ie n \{ \
\h '-04'\(bu \h '+03'\c
. \}
.el \{ \
.sp -1
.IP \(bu 2 .3
. \}
2024-09-03 19:15:59 +02:00
. \" mariadb-dump: skip-tz-utc option
. \" skip-tz-utc option: mariadb-dump
2015-09-09 14:32:52 +02:00
\fB \- \- skip\- tz\- utc\fR
.sp
MDEV-23789: Fix unnecessary acute accents in man pages
The man pages has several places where \' is intended to escape the single
quote and just print '. However, in reality this will print an ` (acute
accent). Fix this by removing excess backslashes. Also remove some excess
& in front of dots, such escaping is also unnecessary.
Also join several lines to avoid lone words in quotes to be read by groff
as macros when they are just text.
In a table (t{}) the content must be on new lines separately, so groff
will try to read them as macros too, so use \(aq that renders to '
(single quote).
This error was originally detected by Lintian:
https://lintian.debian.org/tags/acute-accent-in-manual-page
Example of man page sections before and after:
Make a backup of each table´s data file using the name tbl_name.OLD.
->
Make a backup of each table's data file using the name tbl_name.OLD.
A typical debug_options string is ´d:t:o,file_name´.
The default is ´d:t:o,/tmp/my_print_defaults.trace´.
->
A typical debug_options string is 'd:t:o,file_name'.
The default is 'd:t:o,/tmp/my_print_defaults.trace'.
shell> mysql --xml -uroot -e "SHOW VARIABLES LIKE ´version%´"
<?xml version="1.0"?>
<resultset statement="SHOW VARIABLES LIKE ´version%´" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
->
shell> mysql --xml -uroot -e "SHOW VARIABLES LIKE 'version%'"
<?xml version="1.0"?>
<resultset statement="SHOW VARIABLES LIKE 'version%'" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
This command was used to validate no man pages have syntax errors:
for x in *.?
do
echo "##### $x #####"
LC_ALL=C.UTF-8 MANROFFSEQ='' MANWIDTH=80 man --warnings -E UTF-8 -l -Tutf8 -Z $x >/dev/null
done
The man pages are not perfect after this, there are still a lot of
suboptimal syntax, but this helps towards better man pages.
All new code of the whole pull request, including one or several files
that are either new files or modified ones, are contributed under the
BSD-new license. I am contributing on behalf of my employer Amazon Web
Services, Inc.
2023-03-11 13:01:39 -08:00
Disable the
2015-09-09 14:32:52 +02:00
\fB \- \- tz\- utc\fR
option\& .
.RE
.sp
.RS 4
.ie n \{ \
\h '-04'\(bu \h '+03'\c
. \}
.el \{ \
.sp -1
.IP \(bu 2 .3
. \}
2024-09-03 19:15:59 +02:00
. \" mariadb-dump: socket option
. \" socket option: mariadb-dump
2009-05-25 11:59:47 +02:00
\fB \- \- socket=\fR \fB \fI path\fR \fR ,
\fB \- S \fR \fB \fI path\fR \fR
.sp
For connections to
2009-09-16 14:03:18 +02:00
localhost, the Unix socket file to use, or, on Windows, the name of the named pipe to use\& .
2021-05-10 11:10:53 -06:00
Forces --protocol=socket when specified on the command line without other connection properties; on Windows, forces --protocol=pipe\& .
2009-09-16 14:03:18 +02:00
.RE
.sp
.RS 4
.ie n \{ \
\h '-04'\(bu \h '+03'\c
. \}
.el \{ \
.sp -1
.IP \(bu 2 .3
. \}
2024-09-03 19:15:59 +02:00
. \" mariadb-admin: SSL options
. \" SSL options: mariadb-admin
2009-05-25 11:59:47 +02:00
\fB \- \- ssl\fR
2015-09-09 14:32:52 +02:00
.sp
MDEV-23789: Fix unnecessary acute accents in man pages
The man pages has several places where \' is intended to escape the single
quote and just print '. However, in reality this will print an ` (acute
accent). Fix this by removing excess backslashes. Also remove some excess
& in front of dots, such escaping is also unnecessary.
Also join several lines to avoid lone words in quotes to be read by groff
as macros when they are just text.
In a table (t{}) the content must be on new lines separately, so groff
will try to read them as macros too, so use \(aq that renders to '
(single quote).
This error was originally detected by Lintian:
https://lintian.debian.org/tags/acute-accent-in-manual-page
Example of man page sections before and after:
Make a backup of each table´s data file using the name tbl_name.OLD.
->
Make a backup of each table's data file using the name tbl_name.OLD.
A typical debug_options string is ´d:t:o,file_name´.
The default is ´d:t:o,/tmp/my_print_defaults.trace´.
->
A typical debug_options string is 'd:t:o,file_name'.
The default is 'd:t:o,/tmp/my_print_defaults.trace'.
shell> mysql --xml -uroot -e "SHOW VARIABLES LIKE ´version%´"
<?xml version="1.0"?>
<resultset statement="SHOW VARIABLES LIKE ´version%´" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
->
shell> mysql --xml -uroot -e "SHOW VARIABLES LIKE 'version%'"
<?xml version="1.0"?>
<resultset statement="SHOW VARIABLES LIKE 'version%'" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
This command was used to validate no man pages have syntax errors:
for x in *.?
do
echo "##### $x #####"
LC_ALL=C.UTF-8 MANROFFSEQ='' MANWIDTH=80 man --warnings -E UTF-8 -l -Tutf8 -Z $x >/dev/null
done
The man pages are not perfect after this, there are still a lot of
suboptimal syntax, but this helps towards better man pages.
All new code of the whole pull request, including one or several files
that are either new files or modified ones, are contributed under the
BSD-new license. I am contributing on behalf of my employer Amazon Web
Services, Inc.
2023-03-11 13:01:39 -08:00
Enable SSL for connection (automatically enabled with other flags). Disable with
2015-09-09 14:32:52 +02:00
\fB \- \- skip-ssl\fR \& .
.RE
.sp
.RS 4
.ie n \{ \
\h '-04'\(bu \h '+03'\c
. \}
.el \{ \
.sp -1
.IP \(bu 2 .3
. \}
2024-09-03 19:15:59 +02:00
. \" mariadb-admin: SSL CA option
. \" SSL CA option: mariadb-admin
2015-09-09 14:32:52 +02:00
\fB \- \- ssl\- ca=\fI name\fR
.sp
CA file in PEM format (check OpenSSL docs, implies
\fB \- \- ssl\fR )\& .
.RE
.sp
.RS 4
.ie n \{ \
\h '-04'\(bu \h '+03'\c
. \}
.el \{ \
.sp -1
.IP \(bu 2 .3
. \}
2024-09-03 19:15:59 +02:00
. \" mariadb-admin: SSL CA Path option
. \" SSL CA Path option: mariadb-admin
2015-09-09 14:32:52 +02:00
\fB \- \- ssl\- capath=\fI name\fR
.sp
CA directory (check OpenSSL docs, implies
\fB \- \- ssl\fR )\& .
.RE
.sp
.RS 4
.ie n \{ \
\h '-04'\(bu \h '+03'\c
. \}
.el \{ \
.sp -1
.IP \(bu 2 .3
. \}
2024-09-03 19:15:59 +02:00
. \" mariadb-admin: SSL Cert option
. \" SSL Cert option: mariadb-admin
2015-09-09 14:32:52 +02:00
\fB \- \- ssl\- cert=\fI name\fR
.sp
X509 cert in PEM format (check OpenSSL docs, implies
\fB \- \- ssl\fR )\& .
.RE
.sp
.RS 4
.ie n \{ \
\h '-04'\(bu \h '+03'\c
. \}
.el \{ \
.sp -1
.IP \(bu 2 .3
. \}
2024-09-03 19:15:59 +02:00
. \" mariadb-admin: SSL Cipher option
. \" SSL Cipher option: mariadb-admin
2015-09-09 14:32:52 +02:00
\fB \- \- ssl\- cipher=\fI name\fR
.sp
SSL cipher to use (check OpenSSL docs, implies
\fB \- \- ssl\fR )\& .
.RE
.sp
.RS 4
.ie n \{ \
\h '-04'\(bu \h '+03'\c
. \}
.el \{ \
.sp -1
.IP \(bu 2 .3
. \}
2024-09-03 19:15:59 +02:00
. \" mariadb-admin: SSL Key option
. \" SSL Key option: mariadb-admin
2015-09-09 14:32:52 +02:00
\fB \- \- ssl\- key=\fI name\fR
.sp
X509 key in PEM format (check OpenSSL docs, implies
\fB \- \- ssl\fR )\& .
.RE
.sp
.RS 4
.ie n \{ \
\h '-04'\(bu \h '+03'\c
. \}
.el \{ \
.sp -1
.IP \(bu 2 .3
. \}
2024-09-03 19:15:59 +02:00
. \" mariadb-admin: SSL Crl option
. \" SSL CRL option: mariadb-admin
2015-09-09 14:32:52 +02:00
\fB \- \- ssl\- crl=\fI name\fR
.sp
Certificate revocation list (check OpenSSL docs, implies
\fB \- \- ssl\fR )\& .
.RE
.sp
.RS 4
.ie n \{ \
\h '-04'\(bu \h '+03'\c
. \}
.el \{ \
.sp -1
.IP \(bu 2 .3
. \}
2024-09-03 19:15:59 +02:00
. \" mariadb-admin: SSL Crlpath option
. \" SSL Crlpath option: mariadb-admin
2015-09-09 14:32:52 +02:00
\fB \- \- ssl\- crlpath=\fI name\fR
.sp
Certificate revocation list path (check OpenSSL docs, implies
\fB \- \- ssl\fR )\& .
.RE
.sp
.RS 4
.ie n \{ \
\h '-04'\(bu \h '+03'\c
. \}
.el \{ \
.sp -1
.IP \(bu 2 .3
. \}
2024-09-03 19:15:59 +02:00
. \" mariadb-admin: SSL Verify Server Cert option
. \" SSL Verify Server Cert option: mariadb-admin
2015-09-09 14:32:52 +02:00
\fB \- \- ssl\- verify\- server\- cert\fR
.sp
Verify server's "Common Name" in its cert against hostname used when connecting. This option is disabled by default\& .
2009-09-16 14:03:18 +02:00
.RE
.sp
.RS 4
.ie n \{ \
\h '-04'\(bu \h '+03'\c
. \}
.el \{ \
.sp -1
.IP \(bu 2 .3
. \}
2024-09-03 19:15:59 +02:00
. \" mariadb-admin: Dump system tables option
. \" Dump system tables option: mariadb-admin
2020-08-30 10:53:20 +10:00
\fB \- \- system=\fR \fB \fI {all, users, plugins, udfs, servers, stats, timezones}\fR \fR
.sp
Dump the system tables in the mysql database in a logical form\& . This option is an empty set by default\& .
.sp
One or more options can be listed in comma separated list\& .
.sp
The options here are:
.sp
.RS 4
.ie n \{ \
\h '-04'\(bu \h '+03'\c
. \}
.el \{ \
.sp -1
.IP \(bu 2 .3
. \}
all \- an alias to enabling all of the below options\& .
.RE
.RS 4
.ie n \{ \
\h '-04'\(bu \h '+03'\c
. \}
.el \{ \
.sp -1
.IP \(bu 2 .3
. \}
users \- the users, roles and their grants outputed as \fB CREATE USER\fB , \fB CREATE ROLE\fR , \fB GRANT\fR , and \fB SET DEFAULT ROLE\fR (\fB ALTER USER\fR for MySQL-8.0+)\& .
.RE
.RS 4
.ie n \{ \
\h '-04'\(bu \h '+03'\c
. \}
.el \{ \
.sp -1
.IP \(bu 2 .3
. \}
plugins \- active plugins of the server outputed as \fB INSTALL PLUGIN\fR \& .
.RE
.RS 4
.ie n \{ \
\h '-04'\(bu \h '+03'\c
. \}
.el \{ \
.sp -1
.IP \(bu 2 .3
. \}
udfs \- user define functions outputed as \fB CREATE FUNCTION\fR \& .
.RE
.RS 4
.ie n \{ \
\h '-04'\(bu \h '+03'\c
. \}
.el \{ \
.sp -1
.IP \(bu 2 .3
. \}
servers \- remote (federated) servers as \fB CREATE SERVER\fR \& .
.RE
.RS 4
.ie n \{ \
\h '-04'\(bu \h '+03'\c
. \}
.el \{ \
.sp -1
.IP \(bu 2 .3
. \}
2021-09-16 20:42:26 +10:00
stats \- statistics tables, InnoDB and Engine Independent Table Statistics (EITS), are dumped as \fB REPLACE INTO\fR (or \fB INSERT IGNORE\fR if \fB \- \- insert\- ignore\fR is specified) statements without (re)creating tables\& .
2020-08-30 10:53:20 +10:00
.RE
.RS 4
.ie n \{ \
\h '-04'\(bu \h '+03'\c
. \}
.el \{ \
.sp -1
.IP \(bu 2 .3
. \}
2021-09-16 20:42:26 +10:00
timezones \- timezone related system tables dumped as \fB REPLACE INTO\fR (or \fB INSERT IGNORE\fR if \fB \- \- insert\- ignore\fR is specified) statements without (re)creating tables\& .
2020-08-30 10:53:20 +10:00
.RE
.sp
2021-09-16 20:42:26 +10:00
The format of the output is affected by \fB \- \- replace\fR and \fB \- \- insert\- ignore\fR \& . The \fB \- \- replace\fR option will output \fB CREATE OR REPLACE\fR
2020-08-30 10:53:20 +10:00
forms of SQL, and also \fB DROP IF EXISTS\fR prior to \fB CREATE\fR , if a \fB CREATE OR REPLACE\fR option isn't available.
.sp
With \fB \- \- system=user\fR (or \fB all\fR ), and \fB \- \- replace\fR , SQL is generated to generate an error if attempting to import the dump with a connection user that is being replaced within the dump\& .
.sp
2021-09-16 20:42:26 +10:00
The \fB \- \- insert\- ignore\fR option will cause \fB CREATE IF NOT EXIST\fR forms of SQL to generated if available.
2020-08-30 10:53:20 +10:00
.sp
2021-09-16 20:42:26 +10:00
For stats, and timezones, \fB \- \- replace\fR and \fB \- \- insert\- ignore\fR have the usual effects.
2020-08-30 10:53:20 +10:00
.sp
Enabling specific options here will cause the relevant tables in the mysql database to be ignored when dumping the mysql database or \fB \- \- all\- databases\fR \& .
.sp
2021-01-22 16:41:40 +11:00
To help in migrating from MySQL to MariaDB, this option is designed to be able to dump system information from MySQL-5\& .7 and 8\& .0 servers\& . SQL generated is also experimentally compatible with MySQL-5\& .7/8\& .0. Mappings of implementation specific grants/plugins isn't always one-to-one however between MariaDB and MySQL and will require manual changes\& .
2020-08-30 10:53:20 +10:00
.sp
.RE
.RS 4
.ie n \{ \
\h '-04'\(bu \h '+03'\c
. \}
.el \{ \
.sp -1
.IP \(bu 2 .3
. \}
2024-09-03 19:15:59 +02:00
. \" mariadb-dump: tab option
. \" tab option: mariadb-dump
2009-05-25 11:59:47 +02:00
\fB \- \- tab=\fR \fB \fI path\fR \fR ,
\fB \- T \fR \fB \fI path\fR \fR
.sp
2010-04-28 15:06:11 +02:00
Produce tab\- separated text\- format data files\& . For each dumped table,
2024-09-03 19:15:59 +02:00
\fB mariadb-dump\fR
2009-05-25 11:59:47 +02:00
creates a
2009-09-16 14:03:18 +02:00
\fI tbl_name\fR \& .sql
2009-05-25 11:59:47 +02:00
file that contains the
CREATE TABLE
2010-04-28 15:06:11 +02:00
statement that creates the table, and the server writes a
2009-09-16 14:03:18 +02:00
\fI tbl_name\fR \& .txt
file that contains its data\& . The option value is the directory in which to write the files\& .
.if n \{ \
2009-05-25 11:59:47 +02:00
.sp
2009-09-16 14:03:18 +02:00
. \}
.RS 4
2024-04-16 10:44:00 +03:00
.it 1
2009-05-25 11:59:47 +02:00
.nr an-no-space-flag 1
.nr an-break-flag 1
.br
2009-09-16 14:03:18 +02:00
.ps +1
2009-05-25 11:59:47 +02:00
\fB Note\fR
2009-09-16 14:03:18 +02:00
.ps -1
.br
2009-05-25 11:59:47 +02:00
This option should be used only when
2024-09-03 19:15:59 +02:00
\fB mariadb-dump\fR
2009-05-25 11:59:47 +02:00
is run on the same machine as the
2024-09-03 19:15:59 +02:00
\fB mariadbd\fR
2009-09-16 14:03:18 +02:00
server\& . You must have the
2009-05-25 11:59:47 +02:00
FILE
2009-09-16 14:03:18 +02:00
privilege, and the server must have permission to write files in the directory that you specify\& .
.sp .5v
.RE
2010-04-28 15:06:11 +02:00
By default, the
\& .txt
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
\fB \- \- fields\- \fR \fB \fI xxx\fR \fR
and
\fB \- \- lines\- terminated\- by\fR
options\& .
.sp
2015-09-09 14:32:52 +02:00
Column values are converted to the character set specified by the
2010-04-28 15:06:11 +02:00
\fB \- \- default\- character\- set\fR
2015-09-09 14:32:52 +02:00
option\& .
2009-09-16 14:03:18 +02:00
.RE
.sp
.RS 4
.ie n \{ \
\h '-04'\(bu \h '+03'\c
. \}
.el \{ \
.sp -1
.IP \(bu 2 .3
. \}
2024-09-03 19:15:59 +02:00
. \" mariadb-dump: tables option
. \" tables option: mariadb-dump
2009-05-25 11:59:47 +02:00
\fB \- \- tables\fR
.sp
Override the
\fB \- \- databases\fR
or
\fB \- B\fR
2009-09-16 14:03:18 +02:00
option\& .
2024-09-03 19:15:59 +02:00
\fB mariadb-dump\fR
2009-09-16 14:03:18 +02:00
regards all name arguments following the option as table names\& .
.RE
.sp
.RS 4
.ie n \{ \
\h '-04'\(bu \h '+03'\c
. \}
.el \{ \
.sp -1
.IP \(bu 2 .3
. \}
2024-09-03 19:15:59 +02:00
. \" mariadb-dump: triggers option
. \" triggers option: mariadb-dump
2009-05-25 11:59:47 +02:00
\fB \- \- triggers\fR
.sp
2010-04-28 15:06:11 +02:00
Include triggers for each dumped table in the output\& . This option is enabled by default; disable it with
2009-09-16 14:03:18 +02:00
\fB \- \- skip\- triggers\fR \& .
.RE
.sp
.RS 4
.ie n \{ \
\h '-04'\(bu \h '+03'\c
. \}
.el \{ \
.sp -1
.IP \(bu 2 .3
. \}
2024-09-03 19:15:59 +02:00
. \" mariadb-dump: tz-utc option
. \" tz-utc option: mariadb-dump
2009-05-25 11:59:47 +02:00
\fB \- \- tz\- utc\fR
.sp
This option enables
TIMESTAMP
2009-09-16 14:03:18 +02:00
columns to be dumped and reloaded between servers in different time zones\& .
2024-09-03 19:15:59 +02:00
\fB mariadb-dump\fR
2009-05-25 11:59:47 +02:00
sets its connection time zone to UTC and adds
MDEV-23789: Fix unnecessary acute accents in man pages
The man pages has several places where \' is intended to escape the single
quote and just print '. However, in reality this will print an ` (acute
accent). Fix this by removing excess backslashes. Also remove some excess
& in front of dots, such escaping is also unnecessary.
Also join several lines to avoid lone words in quotes to be read by groff
as macros when they are just text.
In a table (t{}) the content must be on new lines separately, so groff
will try to read them as macros too, so use \(aq that renders to '
(single quote).
This error was originally detected by Lintian:
https://lintian.debian.org/tags/acute-accent-in-manual-page
Example of man page sections before and after:
Make a backup of each table´s data file using the name tbl_name.OLD.
->
Make a backup of each table's data file using the name tbl_name.OLD.
A typical debug_options string is ´d:t:o,file_name´.
The default is ´d:t:o,/tmp/my_print_defaults.trace´.
->
A typical debug_options string is 'd:t:o,file_name'.
The default is 'd:t:o,/tmp/my_print_defaults.trace'.
shell> mysql --xml -uroot -e "SHOW VARIABLES LIKE ´version%´"
<?xml version="1.0"?>
<resultset statement="SHOW VARIABLES LIKE ´version%´" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
->
shell> mysql --xml -uroot -e "SHOW VARIABLES LIKE 'version%'"
<?xml version="1.0"?>
<resultset statement="SHOW VARIABLES LIKE 'version%'" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
This command was used to validate no man pages have syntax errors:
for x in *.?
do
echo "##### $x #####"
LC_ALL=C.UTF-8 MANROFFSEQ='' MANWIDTH=80 man --warnings -E UTF-8 -l -Tutf8 -Z $x >/dev/null
done
The man pages are not perfect after this, there are still a lot of
suboptimal syntax, but this helps towards better man pages.
All new code of the whole pull request, including one or several files
that are either new files or modified ones, are contributed under the
BSD-new license. I am contributing on behalf of my employer Amazon Web
Services, Inc.
2023-03-11 13:01:39 -08:00
SET TIME_ZONE='+00:00'
2009-09-16 14:03:18 +02:00
to the dump file\& . Without this option,
2009-05-25 11:59:47 +02:00
TIMESTAMP
2010-04-28 15:06:11 +02:00
columns are dumped and reloaded in the time zones local to the source and destination servers, which can cause the values to change if the servers are in different time zones\& .
2009-05-25 11:59:47 +02:00
\fB \- \- tz\- utc\fR
2009-09-16 14:03:18 +02:00
also protects against changes due to daylight saving time\& .
2009-05-25 11:59:47 +02:00
\fB \- \- tz\- utc\fR
2009-09-16 14:03:18 +02:00
is enabled by default\& . To disable it, use
2015-09-09 14:32:52 +02:00
\fB \- \- skip\- tz\- utc\fR \& .
2009-09-16 14:03:18 +02:00
.RE
.sp
.RS 4
.ie n \{ \
\h '-04'\(bu \h '+03'\c
. \}
.el \{ \
.sp -1
.IP \(bu 2 .3
. \}
2024-09-03 19:15:59 +02:00
. \" mariadb-dump: user option
. \" user option: mariadb-dump
2009-05-25 11:59:47 +02:00
\fB \- \- user=\fR \fB \fI user_name\fR \fR ,
\fB \- u \fR \fB \fI user_name\fR \fR
.sp
2015-09-09 14:32:52 +02:00
The MariaDB user name to use when connecting to the server\& .
2009-09-16 14:03:18 +02:00
.RE
.sp
.RS 4
.ie n \{ \
\h '-04'\(bu \h '+03'\c
. \}
.el \{ \
.sp -1
.IP \(bu 2 .3
. \}
2024-09-03 19:15:59 +02:00
. \" mariadb-dump: verbose option
. \" verbose option: mariadb-dump
2009-05-25 11:59:47 +02:00
\fB \- \- verbose\fR ,
\fB \- v\fR
.sp
2009-09-16 14:03:18 +02:00
Verbose mode\& . Print more information about what the program does\& .
.RE
.sp
.RS 4
.ie n \{ \
\h '-04'\(bu \h '+03'\c
. \}
.el \{ \
.sp -1
.IP \(bu 2 .3
. \}
2024-09-03 19:15:59 +02:00
. \" mariadb-dump: version option
. \" version option: mariadb-dump
2009-05-25 11:59:47 +02:00
\fB \- \- version\fR ,
\fB \- V\fR
.sp
2009-09-16 14:03:18 +02:00
Display version information and exit\& .
.RE
.sp
.RS 4
.ie n \{ \
\h '-04'\(bu \h '+03'\c
. \}
.el \{ \
.sp -1
.IP \(bu 2 .3
. \}
2024-09-03 19:15:59 +02:00
. \" mariadb-dump: where option
. \" where option: mariadb-dump
MDEV-23789: Fix unnecessary acute accents in man pages
The man pages has several places where \' is intended to escape the single
quote and just print '. However, in reality this will print an ` (acute
accent). Fix this by removing excess backslashes. Also remove some excess
& in front of dots, such escaping is also unnecessary.
Also join several lines to avoid lone words in quotes to be read by groff
as macros when they are just text.
In a table (t{}) the content must be on new lines separately, so groff
will try to read them as macros too, so use \(aq that renders to '
(single quote).
This error was originally detected by Lintian:
https://lintian.debian.org/tags/acute-accent-in-manual-page
Example of man page sections before and after:
Make a backup of each table´s data file using the name tbl_name.OLD.
->
Make a backup of each table's data file using the name tbl_name.OLD.
A typical debug_options string is ´d:t:o,file_name´.
The default is ´d:t:o,/tmp/my_print_defaults.trace´.
->
A typical debug_options string is 'd:t:o,file_name'.
The default is 'd:t:o,/tmp/my_print_defaults.trace'.
shell> mysql --xml -uroot -e "SHOW VARIABLES LIKE ´version%´"
<?xml version="1.0"?>
<resultset statement="SHOW VARIABLES LIKE ´version%´" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
->
shell> mysql --xml -uroot -e "SHOW VARIABLES LIKE 'version%'"
<?xml version="1.0"?>
<resultset statement="SHOW VARIABLES LIKE 'version%'" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
This command was used to validate no man pages have syntax errors:
for x in *.?
do
echo "##### $x #####"
LC_ALL=C.UTF-8 MANROFFSEQ='' MANWIDTH=80 man --warnings -E UTF-8 -l -Tutf8 -Z $x >/dev/null
done
The man pages are not perfect after this, there are still a lot of
suboptimal syntax, but this helps towards better man pages.
All new code of the whole pull request, including one or several files
that are either new files or modified ones, are contributed under the
BSD-new license. I am contributing on behalf of my employer Amazon Web
Services, Inc.
2023-03-11 13:01:39 -08:00
\fB \- \- where='\fR \fB \fI where_condition\fR \fR \fB '\fR ,
\fB \- w '\fR \fB \fI where_condition\fR \fR \fB '\fR
2009-05-25 11:59:47 +02:00
.sp
Dump only rows selected by the given
WHERE
2009-09-16 14:03:18 +02:00
condition\& . Quotes around the condition are mandatory if it contains spaces or other characters that are special to your command interpreter\& .
2009-05-25 11:59:47 +02:00
.sp
Examples:
.sp
2009-09-16 14:03:18 +02:00
.if n \{ \
.RS 4
. \}
2009-05-25 11:59:47 +02:00
.nf
MDEV-23789: Fix unnecessary acute accents in man pages
The man pages has several places where \' is intended to escape the single
quote and just print '. However, in reality this will print an ` (acute
accent). Fix this by removing excess backslashes. Also remove some excess
& in front of dots, such escaping is also unnecessary.
Also join several lines to avoid lone words in quotes to be read by groff
as macros when they are just text.
In a table (t{}) the content must be on new lines separately, so groff
will try to read them as macros too, so use \(aq that renders to '
(single quote).
This error was originally detected by Lintian:
https://lintian.debian.org/tags/acute-accent-in-manual-page
Example of man page sections before and after:
Make a backup of each table´s data file using the name tbl_name.OLD.
->
Make a backup of each table's data file using the name tbl_name.OLD.
A typical debug_options string is ´d:t:o,file_name´.
The default is ´d:t:o,/tmp/my_print_defaults.trace´.
->
A typical debug_options string is 'd:t:o,file_name'.
The default is 'd:t:o,/tmp/my_print_defaults.trace'.
shell> mysql --xml -uroot -e "SHOW VARIABLES LIKE ´version%´"
<?xml version="1.0"?>
<resultset statement="SHOW VARIABLES LIKE ´version%´" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
->
shell> mysql --xml -uroot -e "SHOW VARIABLES LIKE 'version%'"
<?xml version="1.0"?>
<resultset statement="SHOW VARIABLES LIKE 'version%'" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
This command was used to validate no man pages have syntax errors:
for x in *.?
do
echo "##### $x #####"
LC_ALL=C.UTF-8 MANROFFSEQ='' MANWIDTH=80 man --warnings -E UTF-8 -l -Tutf8 -Z $x >/dev/null
done
The man pages are not perfect after this, there are still a lot of
suboptimal syntax, but this helps towards better man pages.
All new code of the whole pull request, including one or several files
that are either new files or modified ones, are contributed under the
BSD-new license. I am contributing on behalf of my employer Amazon Web
Services, Inc.
2023-03-11 13:01:39 -08:00
\- \- where="user='jimf'"
2009-05-25 11:59:47 +02:00
\- w"userid>1"
\- w"userid<1"
.fi
2009-09-16 14:03:18 +02:00
.if n \{ \
.RE
. \}
2009-05-25 11:59:47 +02:00
.RE
2009-09-16 14:03:18 +02:00
.sp
.RS 4
.ie n \{ \
\h '-04'\(bu \h '+03'\c
. \}
.el \{ \
.sp -1
.IP \(bu 2 .3
. \}
2024-09-03 19:15:59 +02:00
. \" mariadb-dump: xml option
. \" xml option: mariadb-dump
2009-05-25 11:59:47 +02:00
\fB \- \- xml\fR ,
\fB \- X\fR
.sp
2009-09-16 14:03:18 +02:00
Write dump output as well\- formed XML\& .
2009-05-25 11:59:47 +02:00
.sp
MDEV-23789: Fix unnecessary acute accents in man pages
The man pages has several places where \' is intended to escape the single
quote and just print '. However, in reality this will print an ` (acute
accent). Fix this by removing excess backslashes. Also remove some excess
& in front of dots, such escaping is also unnecessary.
Also join several lines to avoid lone words in quotes to be read by groff
as macros when they are just text.
In a table (t{}) the content must be on new lines separately, so groff
will try to read them as macros too, so use \(aq that renders to '
(single quote).
This error was originally detected by Lintian:
https://lintian.debian.org/tags/acute-accent-in-manual-page
Example of man page sections before and after:
Make a backup of each table´s data file using the name tbl_name.OLD.
->
Make a backup of each table's data file using the name tbl_name.OLD.
A typical debug_options string is ´d:t:o,file_name´.
The default is ´d:t:o,/tmp/my_print_defaults.trace´.
->
A typical debug_options string is 'd:t:o,file_name'.
The default is 'd:t:o,/tmp/my_print_defaults.trace'.
shell> mysql --xml -uroot -e "SHOW VARIABLES LIKE ´version%´"
<?xml version="1.0"?>
<resultset statement="SHOW VARIABLES LIKE ´version%´" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
->
shell> mysql --xml -uroot -e "SHOW VARIABLES LIKE 'version%'"
<?xml version="1.0"?>
<resultset statement="SHOW VARIABLES LIKE 'version%'" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
This command was used to validate no man pages have syntax errors:
for x in *.?
do
echo "##### $x #####"
LC_ALL=C.UTF-8 MANROFFSEQ='' MANWIDTH=80 man --warnings -E UTF-8 -l -Tutf8 -Z $x >/dev/null
done
The man pages are not perfect after this, there are still a lot of
suboptimal syntax, but this helps towards better man pages.
All new code of the whole pull request, including one or several files
that are either new files or modified ones, are contributed under the
BSD-new license. I am contributing on behalf of my employer Amazon Web
Services, Inc.
2023-03-11 13:01:39 -08:00
\fB NULL\fR \fB , \fR \fB 'NULL'\fR \fB , and Empty Values\fR : For a column named
\fI column_name\fR , the NULL value, an empty string, and the string value 'NULL'
2009-09-16 14:03:18 +02:00
are distinguished from one another in the output generated by this option as follows\& .
2009-05-25 11:59:47 +02:00
.TS
allbox tab(:);
2014-07-24 09:51:51 +02:00
l lx.
2009-05-25 11:59:47 +02:00
T{
\fB Value\fR :
T}:T{
\fB XML Representation\fR :
T}
T{
NULL (\fI unknown value\fR )
T}:T{
2009-09-16 14:03:18 +02:00
<field name="\fI column_name\fR " xsi:nil="true" />
2009-05-25 11:59:47 +02:00
T}
T{
MDEV-23789: Fix unnecessary acute accents in man pages
The man pages has several places where \' is intended to escape the single
quote and just print '. However, in reality this will print an ` (acute
accent). Fix this by removing excess backslashes. Also remove some excess
& in front of dots, such escaping is also unnecessary.
Also join several lines to avoid lone words in quotes to be read by groff
as macros when they are just text.
In a table (t{}) the content must be on new lines separately, so groff
will try to read them as macros too, so use \(aq that renders to '
(single quote).
This error was originally detected by Lintian:
https://lintian.debian.org/tags/acute-accent-in-manual-page
Example of man page sections before and after:
Make a backup of each table´s data file using the name tbl_name.OLD.
->
Make a backup of each table's data file using the name tbl_name.OLD.
A typical debug_options string is ´d:t:o,file_name´.
The default is ´d:t:o,/tmp/my_print_defaults.trace´.
->
A typical debug_options string is 'd:t:o,file_name'.
The default is 'd:t:o,/tmp/my_print_defaults.trace'.
shell> mysql --xml -uroot -e "SHOW VARIABLES LIKE ´version%´"
<?xml version="1.0"?>
<resultset statement="SHOW VARIABLES LIKE ´version%´" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
->
shell> mysql --xml -uroot -e "SHOW VARIABLES LIKE 'version%'"
<?xml version="1.0"?>
<resultset statement="SHOW VARIABLES LIKE 'version%'" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
This command was used to validate no man pages have syntax errors:
for x in *.?
do
echo "##### $x #####"
LC_ALL=C.UTF-8 MANROFFSEQ='' MANWIDTH=80 man --warnings -E UTF-8 -l -Tutf8 -Z $x >/dev/null
done
The man pages are not perfect after this, there are still a lot of
suboptimal syntax, but this helps towards better man pages.
All new code of the whole pull request, including one or several files
that are either new files or modified ones, are contributed under the
BSD-new license. I am contributing on behalf of my employer Amazon Web
Services, Inc.
2023-03-11 13:01:39 -08:00
\(aq \(aq (\fI empty string\fR )
2009-05-25 11:59:47 +02:00
T}:T{
2009-09-16 14:03:18 +02:00
<field name="\fI column_name\fR "></field>
2009-05-25 11:59:47 +02:00
T}
T{
MDEV-23789: Fix unnecessary acute accents in man pages
The man pages has several places where \' is intended to escape the single
quote and just print '. However, in reality this will print an ` (acute
accent). Fix this by removing excess backslashes. Also remove some excess
& in front of dots, such escaping is also unnecessary.
Also join several lines to avoid lone words in quotes to be read by groff
as macros when they are just text.
In a table (t{}) the content must be on new lines separately, so groff
will try to read them as macros too, so use \(aq that renders to '
(single quote).
This error was originally detected by Lintian:
https://lintian.debian.org/tags/acute-accent-in-manual-page
Example of man page sections before and after:
Make a backup of each table´s data file using the name tbl_name.OLD.
->
Make a backup of each table's data file using the name tbl_name.OLD.
A typical debug_options string is ´d:t:o,file_name´.
The default is ´d:t:o,/tmp/my_print_defaults.trace´.
->
A typical debug_options string is 'd:t:o,file_name'.
The default is 'd:t:o,/tmp/my_print_defaults.trace'.
shell> mysql --xml -uroot -e "SHOW VARIABLES LIKE ´version%´"
<?xml version="1.0"?>
<resultset statement="SHOW VARIABLES LIKE ´version%´" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
->
shell> mysql --xml -uroot -e "SHOW VARIABLES LIKE 'version%'"
<?xml version="1.0"?>
<resultset statement="SHOW VARIABLES LIKE 'version%'" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
This command was used to validate no man pages have syntax errors:
for x in *.?
do
echo "##### $x #####"
LC_ALL=C.UTF-8 MANROFFSEQ='' MANWIDTH=80 man --warnings -E UTF-8 -l -Tutf8 -Z $x >/dev/null
done
The man pages are not perfect after this, there are still a lot of
suboptimal syntax, but this helps towards better man pages.
All new code of the whole pull request, including one or several files
that are either new files or modified ones, are contributed under the
BSD-new license. I am contributing on behalf of my employer Amazon Web
Services, Inc.
2023-03-11 13:01:39 -08:00
\(aq NULL\(aq (\fI string value\fR )
2009-05-25 11:59:47 +02:00
T}:T{
2009-09-16 14:03:18 +02:00
<field name="\fI column_name\fR ">NULL</field>
2009-05-25 11:59:47 +02:00
T}
.TE
2009-09-16 14:03:18 +02:00
.sp 1
2015-09-09 14:32:52 +02:00
The output from the
2024-09-03 19:15:59 +02:00
\fB mariadb\fR
2009-05-25 11:59:47 +02:00
client when run using the
\fB \- \- xml\fR
2010-04-28 15:06:11 +02:00
option also follows the preceding rules\& . (See
2024-09-03 19:15:59 +02:00
the section called \(lq MARIADB OPTIONS\(rq \& .)
2009-05-25 11:59:47 +02:00
.sp
2015-09-09 14:32:52 +02:00
XML output from
2024-09-03 19:15:59 +02:00
\fB mariadb-dump\fR
2009-05-25 11:59:47 +02:00
includes the XML namespace, as shown here:
.sp
2009-09-16 14:03:18 +02:00
.if n \{ \
.RS 4
. \}
2009-05-25 11:59:47 +02:00
.nf
2024-09-03 19:15:59 +02:00
shell> \fB mariadb-dump \- \- xml \- u root world City\fR
2009-09-16 14:03:18 +02:00
<?xml version="1\& .0"?>
2024-09-03 19:15:59 +02:00
<mariadb-dump xmlns:xsi="http://www\& .w3\& .org/2001/XMLSchema\- instance">
2009-05-25 11:59:47 +02:00
<database name="world">
<table_structure name="City">
<field Field="ID" Type="int(11)" Null="NO" Key="PRI" Extra="auto_increment" />
<field Field="Name" Type="char(35)" Null="NO" Key="" Default="" Extra="" />
<field Field="CountryCode" Type="char(3)" Null="NO" Key="" Default="" Extra="" />
<field Field="District" Type="char(20)" Null="NO" Key="" Default="" Extra="" />
<field Field="Population" Type="int(11)" Null="NO" Key="" Default="0" Extra="" />
2010-04-28 15:06:11 +02:00
<key Table="City" Non_unique="0" Key_name="PRIMARY" Seq_in_index="1" Column_name="ID"
Collation="A" Cardinality="4079" Null="" Index_type="BTREE" Comment="" />
<options Name="City" Engine="MyISAM" Version="10" Row_format="Fixed" Rows="4079"
Avg_row_length="67" Data_length="273293" Max_data_length="18858823439613951"
Index_length="43008" Data_free="0" Auto_increment="4080"
Create_time="2007\- 03\- 31 01:47:01" Update_time="2007\- 03\- 31 01:47:02"
Collation="latin1_swedish_ci" Create_options="" Comment="" />
2009-05-25 11:59:47 +02:00
</table_structure>
<table_data name="City">
<row>
<field name="ID">1</field>
<field name="Name">Kabul</field>
<field name="CountryCode">AFG</field>
<field name="District">Kabol</field>
<field name="Population">1780000</field>
</row>
2009-09-16 14:03:18 +02:00
\fI \& .\& .\& .\fR
2009-05-25 11:59:47 +02:00
<row>
<field name="ID">4079</field>
<field name="Name">Rafah</field>
<field name="CountryCode">PSE</field>
<field name="District">Rafah</field>
<field name="Population">92020</field>
</row>
</table_data>
</database>
2024-09-03 19:15:59 +02:00
</mariadb-dump>
2009-05-25 11:59:47 +02:00
.fi
2009-09-16 14:03:18 +02:00
.if n \{ \
2009-05-25 11:59:47 +02:00
.RE
2009-09-16 14:03:18 +02:00
. \}
2009-05-25 11:59:47 +02:00
.sp
.RE
.PP
You can also set the following variables by using
\fB \- \- \fR \fB \fI var_name\fR \fR \fB =\fR \fB \fI value\fR \fR
syntax:
2009-09-16 14:03:18 +02:00
.sp
.RS 4
.ie n \{ \
\h '-04'\(bu \h '+03'\c
. \}
.el \{ \
.sp -1
.IP \(bu 2 .3
. \}
2009-05-25 11:59:47 +02:00
max_allowed_packet
.sp
2009-09-16 14:03:18 +02:00
The maximum size of the buffer for client/server communication\& . The maximum is 1GB\& .
.RE
.sp
.RS 4
.ie n \{ \
\h '-04'\(bu \h '+03'\c
. \}
.el \{ \
.sp -1
.IP \(bu 2 .3
. \}
2022-07-29 16:07:42 +10:00
max_statement_time
.sp
A query that has taken more than max_statement_time seconds will be aborted and the backup will
fail\& . The argument will be treated as a decimal value with microsecond precision\& . A value
of 0 (default) means no timeout\& . The maximum timeout is 31536000 seconds\& .
.RE
.sp
.RS 4
.ie n \{ \
\h '-04'\(bu \h '+03'\c
. \}
.el \{ \
.sp -1
.IP \(bu 2 .3
. \}
2009-05-25 11:59:47 +02:00
net_buffer_length
.sp
2010-04-28 15:06:11 +02:00
The initial size of the buffer for client/server communication\& . When creating multiple\- row
INSERT
statements (as with the
2009-05-25 11:59:47 +02:00
\fB \- \- extended\- insert\fR
or
2010-04-28 15:06:11 +02:00
\fB \- \- opt\fR
option),
2024-09-03 19:15:59 +02:00
\fB mariadb-dump\fR
2009-05-25 11:59:47 +02:00
creates rows up to
net_buffer_length
2009-09-16 14:03:18 +02:00
length\& . If you increase this variable, you should also ensure that the
2009-05-25 11:59:47 +02:00
net_buffer_length
2015-09-09 14:32:52 +02:00
variable in the MariaDB server is at least this large\& .
2009-05-25 11:59:47 +02:00
.RE
.PP
2010-04-28 15:06:11 +02:00
A common use of
2024-09-03 19:15:59 +02:00
\fB mariadb-dump\fR
2010-04-28 15:06:11 +02:00
is for making a backup of an entire database:
2009-05-25 11:59:47 +02:00
.sp
2009-09-16 14:03:18 +02:00
.if n \{ \
.RS 4
. \}
2009-05-25 11:59:47 +02:00
.nf
2024-09-03 19:15:59 +02:00
shell> \fB mariadb-dump \fR \fB \fI db_name\fR \fR \fB > \fR \fB \fI backup\- file\& .sql\fR \fR
2009-05-25 11:59:47 +02:00
.fi
2009-09-16 14:03:18 +02:00
.if n \{ \
2009-05-25 11:59:47 +02:00
.RE
2009-09-16 14:03:18 +02:00
. \}
2009-05-25 11:59:47 +02:00
.PP
2010-04-28 15:06:11 +02:00
You can load the dump file back into the server like this:
2009-05-25 11:59:47 +02:00
.sp
2009-09-16 14:03:18 +02:00
.if n \{ \
.RS 4
. \}
2009-05-25 11:59:47 +02:00
.nf
2024-09-03 19:15:59 +02:00
shell> \fB mariadb \fR \fB \fI db_name\fR \fR \fB < \fR \fB \fI backup\- file\& .sql\fR \fR
2009-05-25 11:59:47 +02:00
.fi
2009-09-16 14:03:18 +02:00
.if n \{ \
2009-05-25 11:59:47 +02:00
.RE
2009-09-16 14:03:18 +02:00
. \}
2009-05-25 11:59:47 +02:00
.PP
Or like this:
.sp
2009-09-16 14:03:18 +02:00
.if n \{ \
.RS 4
. \}
2009-05-25 11:59:47 +02:00
.nf
2024-09-03 19:15:59 +02:00
shell> \fB mariadb \- e "source \fR \fB \fI /path\- to\- backup/backup\- file\& .sql\fR \fR \fB " \fR \fB \fI db_name\fR \fR
2009-05-25 11:59:47 +02:00
.fi
2009-09-16 14:03:18 +02:00
.if n \{ \
2009-05-25 11:59:47 +02:00
.RE
2009-09-16 14:03:18 +02:00
. \}
2009-05-25 11:59:47 +02:00
.PP
2024-09-03 19:15:59 +02:00
\fB mariadb-dump\fR
2015-09-09 14:32:52 +02:00
is also very useful for populating databases by copying data from one MariaDB server to another:
2009-05-25 11:59:47 +02:00
.sp
2009-09-16 14:03:18 +02:00
.if n \{ \
.RS 4
. \}
2009-05-25 11:59:47 +02:00
.nf
2024-09-03 19:15:59 +02:00
shell> \fB mariadb-dump \- \- opt \fR \fB \fI db_name\fR \fR \fB | mariadb \- \- host=\fR \fB \fI remote_host\fR \fR \fB \- C \fR \fB \fI db_name\fR \fR
2009-05-25 11:59:47 +02:00
.fi
2009-09-16 14:03:18 +02:00
.if n \{ \
2009-05-25 11:59:47 +02:00
.RE
2009-09-16 14:03:18 +02:00
. \}
2009-05-25 11:59:47 +02:00
.PP
It is possible to dump several databases with one command:
.sp
2009-09-16 14:03:18 +02:00
.if n \{ \
.RS 4
. \}
2009-05-25 11:59:47 +02:00
.nf
2024-09-03 19:15:59 +02:00
shell> \fB mariadb-dump \- \- databases \fR \fB \fI db_name1\fR \fR \fB [\fR \fB \fI db_name2\fR \fR \fB \& .\& .\& .] > my_databases\& .sql\fR
2009-05-25 11:59:47 +02:00
.fi
2009-09-16 14:03:18 +02:00
.if n \{ \
2009-05-25 11:59:47 +02:00
.RE
2009-09-16 14:03:18 +02:00
. \}
2009-05-25 11:59:47 +02:00
.PP
To dump all databases, use the
\fB \- \- all\- databases\fR
option:
.sp
2009-09-16 14:03:18 +02:00
.if n \{ \
.RS 4
. \}
2009-05-25 11:59:47 +02:00
.nf
2024-09-03 19:15:59 +02:00
shell> \fB mariadb-dump \- \- all\- databases > all_databases\& .sql\fR
2009-05-25 11:59:47 +02:00
.fi
2009-09-16 14:03:18 +02:00
.if n \{ \
2009-05-25 11:59:47 +02:00
.RE
2009-09-16 14:03:18 +02:00
. \}
2009-05-25 11:59:47 +02:00
.PP
For
InnoDB
tables,
2024-09-03 19:15:59 +02:00
\fB mariadb-dump\fR
2009-05-25 11:59:47 +02:00
provides a way of making an online backup:
.sp
2009-09-16 14:03:18 +02:00
.if n \{ \
.RS 4
. \}
2009-05-25 11:59:47 +02:00
.nf
2024-09-03 19:15:59 +02:00
shell> \fB mariadb-dump \- \- all\- databases \- \- single\- transaction > all_databases\& .sql\fR
2009-05-25 11:59:47 +02:00
.fi
2009-09-16 14:03:18 +02:00
.if n \{ \
2009-05-25 11:59:47 +02:00
.RE
2009-09-16 14:03:18 +02:00
. \}
2009-05-25 11:59:47 +02:00
.PP
This backup acquires a global read lock on all tables (using
2009-09-16 14:03:18 +02:00
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 long updating statements are running when the
2009-05-25 11:59:47 +02:00
FLUSH
2015-09-09 14:32:52 +02:00
statement is issued, the MariaDB server may get stalled until those statements finish\& . After that, the dump becomes lock free and does not disturb reads and writes on the tables\& . If the update statements that the MariaDB server receives are short (in terms of execution time), the initial lock period should not be noticeable, even with many updates\& .
2009-05-25 11:59:47 +02:00
.PP
For point\- in\- time recovery (also known as
\(lq roll\- forward,\(rq
2015-09-09 14:32:52 +02:00
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 or at least know the binary log coordinates to which the dump corresponds:
2009-05-25 11:59:47 +02:00
.sp
2009-09-16 14:03:18 +02:00
.if n \{ \
.RS 4
. \}
2009-05-25 11:59:47 +02:00
.nf
2024-09-03 19:15:59 +02:00
shell> \fB mariadb-dump \- \- all\- databases \- \- master\- data=2 > all_databases\& .sql\fR
2009-05-25 11:59:47 +02:00
.fi
2009-09-16 14:03:18 +02:00
.if n \{ \
2009-05-25 11:59:47 +02:00
.RE
2009-09-16 14:03:18 +02:00
. \}
2009-05-25 11:59:47 +02:00
.PP
Or:
.sp
2009-09-16 14:03:18 +02:00
.if n \{ \
.RS 4
. \}
2009-05-25 11:59:47 +02:00
.nf
2024-09-03 19:15:59 +02:00
shell> \fB mariadb-dump \- \- all\- databases \- \- flush\- logs \- \- master\- data=2\fR
2009-09-16 14:03:18 +02:00
\fB > all_databases\& .sql\fR
2009-05-25 11:59:47 +02:00
.fi
2009-09-16 14:03:18 +02:00
.if n \{ \
2009-05-25 11:59:47 +02:00
.RE
2009-09-16 14:03:18 +02:00
. \}
2009-05-25 11:59:47 +02:00
.PP
The
\fB \- \- master\- data\fR
and
\fB \- \- single\- transaction\fR
2010-04-28 15:06:11 +02:00
options can be used simultaneously, which provides a convenient way to make an online backup suitable for use prior to point\- in\- time recovery if tables are stored using the
2009-05-25 11:59:47 +02:00
InnoDB
2009-09-16 14:03:18 +02:00
storage engine\& .
2009-05-25 11:59:47 +02:00
.PP
2024-09-03 19:15:59 +02:00
. \" mariadb-dump: views
. \" mariadb-dump: problems
. \" mariadb-dump: workarounds
2009-05-25 11:59:47 +02:00
.PP
2015-09-09 14:32:52 +02:00
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\& .
2009-05-25 11:59:47 +02:00
.SH "COPYRIGHT"
2009-09-16 14:03:18 +02:00
.br
2009-05-25 11:59:47 +02:00
.PP
2024-09-03 19:15:59 +02:00
Copyright 2007-2008 MySQL AB, 2008-2010 Sun Microsystems, Inc., 2010-2024 MariaDB Foundation
2009-05-25 11:59:47 +02:00
.PP
This documentation is free software; you can redistribute it and/or modify it only under the terms of the GNU General Public License as published by the Free Software Foundation; version 2 of the License.
.PP
This documentation is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details.
.PP
2019-05-11 21:29:06 +03:00
You should have received a copy of the GNU General Public License along with the program; if not, write to the Free Software Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1335 USA or see http://www.gnu.org/licenses/.
2009-09-16 14:03:18 +02:00
.sp
2009-05-25 11:59:47 +02:00
.SH "SEE ALSO"
2015-09-09 14:32:52 +02:00
For more information, please refer to the MariaDB Knowledge Base, available online at https://mariadb.com/kb/
2009-05-25 11:59:47 +02:00
.SH AUTHOR
2015-09-09 14:32:52 +02:00
MariaDB Foundation (http://www.mariadb.org/).