document options that break on disk compatibility with Oracle MySQL

Bug #930571 reported by Stewart Smith on 2012-02-11
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Percona Server moved to
Fix Released
Hrvoje Matijakovic
Fix Released
Hrvoje Matijakovic
Fix Released
Hrvoje Matijakovic

Bug Description

We should have a page in documentation that details all the options that make XtraDB tablespaces not compatible with MySQL.

Taken from Bill Karwin's post to the percona-discussion googlegroups list, this is a start:

I don't think there's a concise list anywhere. AFAIK, the optional features
 of XtraDB on-disk structure that break backward compatibility are:

 Expanded undo slots

 Relocation of the doublewrite buffer (but I'm not sure if this one really
 breaks compatibility)

 Fast checksums

 Page sizes other than 16KiB

 Perhaps some of the XtraDB developers can confirm these, or add to this list
 any other features that also break compatibility.

 Bill Karwin

IIRC there is also log block size.

Tags: doc Edit Tag help

Related branches

Stewart Smith (stewart) on 2012-02-11
Changed in percona-server:
importance: Undecided → Medium
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:
status: In Progress → Fix Committed
assignee: nobody → Hrvoje Matijakovic (hrvojem)

Percona now uses JIRA for bug reports so this bug report is migrated to:

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

Other bug subscribers