Skip to content

Conversation

@ayurchen
Copy link
Contributor

@ayurchen ayurchen commented Apr 6, 2024

(but keep support for it for backward compatibility) The only place where wsrep-lib made use of WSREP_KEY_SHARED is wsrep::append_sr_keys_for_commit() which is used only with protocols >= 4 so we don't need to worry about the protocol version and just change wsrep::key::shared to wsrep::key::reference.

Refs #227

…_REfERENCE

(but keep support for it for backward compatibility)
The only place where wsrep-lib made use of WSREP_KEY_SHARED is
wsrep::append_sr_keys_for_commit() which is used only with protocols >= 4
so we don't need to worry about the protocol version and just change
wsrep::key::shared to wsrep::key::reference.

Refs #227
@ayurchen ayurchen self-assigned this Apr 6, 2024
ret == 0 && j != i->second.end(); ++j)
{
wsrep::key key(wsrep::key::shared);
wsrep::key key(wsrep::key::reference);
Copy link
Contributor

Choose a reason for hiding this comment

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

Reference key is probably too strong here. The purpose of adding shared keys to commit fragment is to create dependency, but changing it to reference key will create a conflict with exclusive.

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