Skip to content

Conversation

@ayurchen
Copy link
Contributor

Fix to read/write seqno to XID in a little-endian format.

@ayurchen ayurchen added this to the 5.6.x-25.11 milestone Mar 28, 2015
sql/wsrep_xid.cc Outdated
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This looks like a time bomb. It would probably be better to change WSREP_XID_PREFIX and do the byteswap if the stored value has the new format.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Does WSREP_XID_PREFIX act as a version ID? If so, then indeed it is better.

…XID prefix as a version ID to distinguish which order XID seqno is stored in.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This introduces unnecessary dependency between InnoDB and MySQL/wsrep code. Setting xid->formatID = -1 in code below is enough to indicate that the XID is null, so WSREP_* macros and wsrep_xid_init() don't have to be included.

@temeo temeo modified the milestones: 5.6.26-25.11, 5.5.45-25.12, 5.6.x-25.12 Aug 26, 2015
@philip-galera philip-galera removed this from the 5.6.27-25.12 milestone Nov 16, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants