consistency check support by total order isolation

Bug #944643 reported by Seppo Jaakola
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
MySQL patches by Codership
Fix Released
Wishlist
Seppo Jaakola
5.5
Fix Released
Wishlist
Seppo Jaakola

Bug Description

Add support for consistency checking by reusing total order isolation semantics

Related branches

Changed in codership-mysql:
status: New → In Progress
importance: Undecided → Wishlist
assignee: nobody → Seppo Jaakola (seppo-jaakola)
milestone: none → 5.5.21-23.5
Revision history for this message
Seppo Jaakola (seppo-jaakola) wrote :

In the first stage, consistency check should be enabled for INSERT...SELECT statements, which are marked by a special comment tag.
However, comment tagging is not simple anymore after MySQL client library is currently filtering comments out. We have some options to provide a workaround for this:
1. provide our own client library
2. completely new SQL syntax for CC
3. declaring CC state by session variable(s)
4. reusing conditional version comment /*!##### structure by piggy bagging WSREP syntax inside
    4A. reserving one magic version number directly for declaring CC state
    4B using magic WSREP version number to declare following comment contents as special WSREP language

Out of these alternatives, for the sake of simplicity, we should use #4A for the first implementation. Then consistency check can be triggered simply by a statement like:

INSERT...SELECT /*!99997*/

The magic CC version number here is 99997. MySQL client library should let that through and current server editions should filter it out

Revision history for this message
Seppo Jaakola (seppo-jaakola) wrote :
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.