fake_changes is poorly documented

Bug #914289 reported by Kenny Gryp on 2012-01-10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Percona Server moved to https://jira.percona.com/projects/PS
Fix Released
Hrvoje Matijakovic
Fix Released
Hrvoje Matijakovic
Fix Released
Hrvoje Matijakovic

Bug Description

The documentation page : http://www.percona.com/doc/percona-server/5.5/management/innodb_fake_changes.html
is not really documentation.

It does not explain the feature properly.

What does the thing do?
How should we use it?
When should we use it?

during a percona internal discussion a blogpost from domas came up who explained it quite nicely:

Related branches

Changed in percona-server:
assignee: nobody → Valentine Gostev (longbow)
Stewart Smith (stewart) on 2012-02-07
Changed in percona-server:
assignee: Valentine Gostev (longbow) → nobody
importance: Undecided → Low
status: New → Triaged
tags: added: doc
Changed in percona-server:
status: Triaged → In Progress
Stewart Smith (stewart) on 2012-02-22
Changed in percona-server:
assignee: nobody → Hrvoje Matijakovic (hrvojem)
status: In Progress → Fix Committed

Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PS-1901

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers