[MDEV-17475] Increase maximum possible value for table_definition_cache to match table_open_cache Created: 2018-10-16 Updated: 2020-08-25 Resolved: 2019-01-16 |
|
| Status: | Closed |
| Project: | MariaDB Server |
| Component/s: | OTHER |
| Affects Version/s: | None |
| Fix Version/s: | 10.4.2, 10.1.38, 10.0.38, 10.2.22, 10.3.13 |
| Type: | Bug | Priority: | Major |
| Reporter: | Valerii Kravchuk | Assignee: | Oleksandr Byelkin |
| Resolution: | Fixed | Votes: | 1 |
| Labels: | None | ||
| Description |
|
In MariaDB 10.0.35+ the maximum possible value of table_open_cache was increased from 512K to 1024K (see https://jira.mariadb.org/browse/MDEV-11429). It makes sense to increase maximum possible value of table_definition_cache accordingly, to help avoid "General error: 1615 Prepared statement needs to be re-prepared" errors in some environments with a lot of tables. |
| Comments |
| Comment by Oleksandr Byelkin [ 2019-01-11 ] |
|
To avoid misinterpretation, what "accordingly" mean hear? (the same, 2 times more, 4 times less) |
| Comment by Oleksandr Byelkin [ 2019-01-11 ] |
|
it should be bigger if view used so 2x or 1.5x |
| Comment by Oleksandr Byelkin [ 2019-01-11 ] |
|
revision-id: 1481d7a58b537d75f0a110e8a0514706adec669e (mariadb-10.0.37-41-g1481d7a58b5)
Allow table definition cache be bigger than open table cache (due to problem with VIEWs and prepared statements). |
| Comment by Sergei Golubchik [ 2019-01-16 ] |
|
ok to push |