[MXS-4717] information_schema is not invalidated as needed Created: 2023-08-16 Updated: 2023-10-10 Resolved: 2023-08-24 |
|
| Status: | Closed |
| Project: | MariaDB MaxScale |
| Component/s: | cache |
| Affects Version/s: | 2.5, 6.4, 22.08, 23.02 |
| Fix Version/s: | 2.5.29, 6.4.10, 22.08.8, 23.02.4 |
| Type: | Bug | Priority: | Major |
| Reporter: | Johan Wikman | Assignee: | Johan Wikman |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Sprint: | MXS-SPRINT-189 |
| Description |
|
A SELECT targeting information_schema will be cached like any other SELECT. However, in that case it should be invalidated e.g. when a table is DROPed. It would probably be best to always exclude SELECTs targeting information_schema. |
| Comments |
| Comment by Johan Wikman [ 2023-08-24 ] |
|
Solved so that result sets related to a table in information_schema are not cached when invalidation is enabled. If invalidation is not enabled, they are cached. |