[MDEV-26124] Minor LOAD INDEX output inconsistencies under XA Created: 2021-07-10 Updated: 2023-04-27 |
|
| Status: | Open |
| Project: | MariaDB Server |
| Component/s: | Storage Engine - InnoDB, XA |
| Affects Version/s: | 10.2, 10.3, 10.4, 10.5, 10.6, 10.7 |
| Fix Version/s: | 10.4, 10.5, 10.6 |
| Type: | Bug | Priority: | Minor |
| Reporter: | Roel Van de Paar | Assignee: | Oleksandr Byelkin |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Description |
|
Whilst it does not seem to affect operation/data, the "Corrupt" error in the output below looks to be incorrect:
Furthermore, the output in 10.2 (and 10.3) for the same commands is somewhat different (single XAER_RMFAIL output instead of repeated):
10.4, 10.5 and 10.6 also have double repeated XAER_RMFAIL messages. It is not clear why the messages are repeated now (could be a regression). It also does matter if the table exists or not, the output is the same. |
| Comments |
| Comment by Marko Mäkelä [ 2021-07-10 ] |
|
This is the first time I became aware of the existence of such syntax. The initial implementation used the keyword PRELOAD. For distributed transactions, InnoDB only allows operations to be executed while the transaction is in the active state. I think that this bug is best fixed by properly disallowing the operation while a distributed transaction is in a non-active state, just like we should do for any operation. InnoDB is only the messenger here, not the culprit. |