[MDEV-32338] session_track_transaction_info=CHARACTERISTICS disables the query cache Created: 2023-10-02 Updated: 2023-11-28 |
|
| Status: | Confirmed |
| Project: | MariaDB Server |
| Component/s: | Query Cache |
| Affects Version/s: | 10.2, 10.3, 10.4, 10.5, 10.6, 10.7, 10.8, 10.9, 10.10, 10.11, 11.0 |
| Fix Version/s: | 10.4, 10.5, 10.6, 10.11, 11.0 |
| Type: | Bug | Priority: | Major |
| Reporter: | markus makela | Assignee: | Oleksandr Byelkin |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Environment: |
Docker images from dockerhub |
||
| Description |
|
With this configuration, the query cache is disabled.
Removing session_track_transaction_info=CHARACTERISTICS makes the query cache work again:
|
| Comments |
| Comment by Sergei Golubchik [ 2023-10-12 ] | ||||||||||||||||||||||||||||
|
Appears to be intentional:
| ||||||||||||||||||||||||||||
| Comment by Oleksandr Byelkin [ 2023-10-12 ] | ||||||||||||||||||||||||||||
|
The problem is that reply of the same SQL can be different depending on how changed other tables in the transaction. The query cache store answer to the user and so there are two ways to deal with it: 1. just do not use it with query cache (now) | ||||||||||||||||||||||||||||
| Comment by markus makela [ 2023-10-12 ] | ||||||||||||||||||||||||||||
|
Perhaps just documenting this or warning about it would be enough. | ||||||||||||||||||||||||||||