Percona Server moved to https://jira.percona.com/projects/PS

Merge lp://qastaging/~hrvojem/percona-server/bug1406482-5.5 into lp://qastaging/percona-server/5.5

  1. bug1406482-5.5
  2. Merge into 5.5
Proposed by Hrvoje Matijakovic
Status: Merged
Approved by: Laurynas Biveinis
Approved revision: no longer in the source branch.
Merged at revision: 729
Proposed branch: lp://qastaging/~hrvojem/percona-server/bug1406482-5.5
Merge into: lp://qastaging/percona-server/5.5
Diff against target: 29 lines (+6/-2)
1 file modified
doc/source/reliability/crash_resistant_replication.rst (+6/-2)
To merge this branch: bzr merge lp://qastaging/~hrvojem/percona-server/bug1406482-5.5
Reviewer Review Type Date Requested Status
Laurynas Biveinis (community) Approve
Review via email: mp+246568@code.qastaging.launchpad.net
To post a comment you must log in.
Revision history for this message
Laurynas Biveinis (laurynas-biveinis) wrote :

The page now mentions the Percona option several times without the MySQL option. It also does not really have a section on how to enable the feature, so I suggest to add a section "Use" before "Restrictions": "To enable the feature, the following options need to be enabled together: innodb_recovery_update_relay_log, and relay_log_recovery (link).". Then, when one option is mentioned, the other should be mentioned too if it makes sense, i.e. in the Restrictions section.

Please also make sure the page use the new Percona option name consistently, it still mentions innodb_overwrite_relay_log_info.

review: Needs Fixing
Revision history for this message
Laurynas Biveinis (laurynas-biveinis) :
review: Approve

Preview Diff

[H/L] Next/Prev Comment, [J/K] Next/Prev File, [N/P] Next/Prev Hunk
The diff is not available at this time. You can reload the page or download it.

Subscribers

People subscribed via source and target branches