[MDEV-16251] Query caching should not be enabled by default in apt packages Created: 2018-05-22  Updated: 2020-06-14  Resolved: 2020-06-14

Status: Closed
Project: MariaDB Server
Component/s: Platform Debian
Affects Version/s: 5.5, 10.0, 10.1, 10.2, 10.3
Fix Version/s: 10.5.4

Type: Bug Priority: Major
Reporter: Benedikt Waldvogel Assignee: Otto Kekäläinen
Resolution: Fixed Votes: 0
Labels: apt, debian

Issue Links:
Relates
relates to MDEV-16087 Inconsistent SELECT results when quer... Closed
relates to MDEV-22795 Query cache still activated in Ubutu ... Closed

 Description   

Query caching is enabled in MariaDB apt packages although it’s not the default behaviour of a vanilla MariaDB server (see the documentation of query_cache_type).
This probably happens because query_cache_size is set to a non-default value.

It is especially problematic since query caching has a regression in MariaDB 10.2.x and 10.3.x which causes SELECT to return wrong results in certain scenarios (see MDEV-16087 for details).

 Comments   
Comment by Otto Kekäläinen [ 2018-08-05 ]

With MDEV-16087 fixed, should query cache be now enabled by default or not?

I see that in upstream Debian packaging the my.cnf ships with query_cache_size=64M and in downstream official Debian packages there is query_cache_size=16M

Comment by Benedikt Waldvogel [ 2018-12-28 ]

With MDEV-16087 fixed, should query cache be now enabled by default or not?

In my opinion the apt packages should use the default configuration.
I.e. default query_cache_size and thus query caching disabled.

Comment by Otto Kekäläinen [ 2020-04-23 ]

WIP in https://github.com/MariaDB/server/pull/1504

Comment by Otto Kekäläinen [ 2020-06-14 ]

Closed via aaaf005ce61a543f1a1470b179ccb535698b36ef and bb8477778b72f047437b2a03a2bd38997e155f10 when #1504 was merged.

Generated at Thu Feb 08 08:27:31 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.