[DOC] Wrong mysql_dump command in documentation
Bug #1025541 reported by
Volans
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Percona Server moved to https://jira.percona.com/projects/PS |
Fix Released
|
Undecided
|
Hrvoje Matijakovic | ||
| 5.5 |
Fix Released
|
Undecided
|
Hrvoje Matijakovic | ||
Bug Description
[In:Percona Server Documentation]
In the "Percona Sever In-Place Upgrading Guide: From 5.1 to 5.5" ( http://
$ mysql_dump --user=root -p --all-databases --triggers > mydata.sql
where "mysql_dump" should be replaced with "mysqldump".
I'm wondering also why there is specified the "--triggers" option that is TRUE by default and not the "--routines" option that is FALSE by default. The resulting backup will be missing all the PROCEDUREs and FUNCTIONs!
Related branches
lp:~hrvojem/percona-server/bug1025541-5.5
- Laurynas Biveinis (community): Approve
-
Diff: 3724 lines (+3361/-31)17 files modified.bzrignore (+0/-1)
doc/Makefile (+6/-0)
doc/source/diagnostics/innodb_deadlock_count.rst (+1/-1)
doc/source/diagnostics/innodb_show_status.rst (+14/-14)
doc/source/management/innodb_dict_size_limit.rst (+1/-1)
doc/source/percona-theme/layout.html (+407/-0)
doc/source/percona-theme/searchbox.html (+22/-0)
doc/source/percona-theme/static/default.css_t (+433/-0)
doc/source/percona-theme/static/jquery.min.js (+154/-0)
doc/source/percona-theme/static/percona.com.css (+1850/-0)
doc/source/percona-theme/static/percona.com.js (+269/-0)
doc/source/percona-theme/static/sidebar.js (+151/-0)
doc/source/percona-theme/theme.conf (+32/-0)
doc/source/release-notes/Percona-Server-5.5.8-20.0.rst (+1/-1)
doc/source/scalability/innodb_io_55.rst (+7/-7)
doc/source/scalability/innodb_split_buf_pool_mutex.rst (+1/-1)
doc/source/upgrading_guide_51_55.rst (+12/-5)
| Changed in percona-server: | |
| assignee: | nobody → Hrvoje Matijakovic (hrvojem) |
Revision history for this message
| Shahriyar Rzayev (rzayev-sehriyar) wrote | #1 |
To post a comment you must log in.
Percona now uses JIRA for bug reports so this bug report is migrated to: https:/