Fix planning of volatile transactions with uncommitted effects#2505
Conversation
|
⚪
|
|
⚪
|
4e31462 to
5a1e8dc
Compare
|
⚪
|
|
⚪
|
|
⚪
|
|
⚪
|
4e31462 to
5a1e8dc
Compare
|
⚪
|
|
⚪
|
Changelog entry
...
Changelog category
Additional information
We checked for volatile tx too early, with uncommitted writes missing from datashardTxs, which caused transaction to run as non-volatile even when volatile transactions are enabled. This patch changes BuildDatashardTxs to prepare all basic transaction bodies first, before deciding whether it should be volatile, and finally filling sending/receiving shard sets when needed.
Fixes #2504.