Percona Server with XtraDB

fake_changes is poorly documented

Reported by Kenny Gryp on 2012-01-10
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Percona Server
Low
Hrvoje Matijakovic
5.1
Low
Hrvoje Matijakovic
5.5
Low
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:
http://dom.as/2011/12/03/replication-prefetching/

Related branches

lp:~hrvojem/percona-server/bug930571-5.1
Merged into lp:percona-server/5.1 at revision 432
Stewart Smith (community): Approve on 2012-04-02
Alexey Kopytov: Pending requested 2012-03-27
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
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers